Processed: found 848339 in unbound/1.6.0-1

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 848339 unbound/1.6.0-1 Bug #848339 [libunbound2] unbound-anchor: libunbound.so.2 unknown symbol fake_dsa Marked as found in versions unbound/1.6.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 848339:

Processed: missing fake_dsa symbol makes reverse dependencies FTBFS

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 848339 serious Bug #848339 [unbound-anchor] unbound-anchor: libunbound.so.2 unknown symbol fake_dsa Severity set to 'serious' from 'important' > reassign 848339 libunbound2 Bug #848339 [unbound-anchor] unbound-anchor: libunbound.so.2

Processed: xmacro: block ITA 832150 by RFS 848384

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 832150 by 848384 Bug #832150 [wnpp] ITA: xmacro -- Record / Play keystrokes and mouse movements in X displays 832150 was not blocked by any bugs. 832150 was not blocking any bugs. Added blocking bug(s) of 832150: 848384 > stop Stopping

Bug#841511: marked as done (python-bitbucket-api, python-bitbucket: error when trying to install together)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 03:09:02 + with message-id and subject line Bug#841511: fixed in python-bitbucket-api 0.5.0-2 has caused the Debian Bug report #841511, regarding python-bitbucket-api, python-bitbucket: error when trying to install

Bug#848389: derby: Fails to build from source

2016-12-16 Thread Jeremy Bicha
Package: derby Version: 10.13.1.1-1 Severity: serious derby fails to build from source. It looks to me like it's failing because it's trying to connect to an external website and fails when it can't load the URL. I recommend doing a source-only upload next time to detect these issues sooner.

Bug#841511: marked as pending

2016-12-16 Thread 陳昌倬
tag 841511 pending thanks Hello, Bug #841511 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/python-bitbucket-api.git;a=commitdiff;h=72c83a9 --- commit

Processed: Bug#841511 marked as pending

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 841511 pending Bug #841511 [python-bitbucket-api,python-bitbucket] python-bitbucket-api, python-bitbucket: error when trying to install together Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#846624: marked as done (debconf: invalid version in maintainer script)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:48:42 + with message-id and subject line Bug#844701: fixed in dpkg 1.18.16 has caused the Debian Bug report #844701, regarding debconf: invalid version in maintainer script to be marked as done. This means that you

Bug#846564: marked as done (dpkg-deb: 'compressing tar member: lzma error: Cannot allocate memory' on 32-bit architectures on dpkg-deb -Zxz -Sextreme -z9)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:48:43 + with message-id and subject line Bug#846564: fixed in dpkg 1.18.16 has caused the Debian Bug report #846564, regarding dpkg-deb: 'compressing tar member: lzma error: Cannot allocate memory' on 32-bit

Bug#828231: marked as done (alpine: FTBFS with openssl 1.1.0)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:48:34 + with message-id and subject line Bug#828231: fixed in alpine 2.20+dfsg1-3 has caused the Debian Bug report #828231, regarding alpine: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Bug#844701: marked as done (dpkg-maintscript-helper: Version comparison fails for supposedly valid versions)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:48:42 + with message-id and subject line Bug#844701: fixed in dpkg 1.18.16 has caused the Debian Bug report #844701, regarding dpkg-maintscript-helper: Version comparison fails for supposedly valid versions to be

Processed: Pending fixes for bugs in the libdata-dumpxml-perl package

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 817596 + pending Bug #817596 [src:libdata-dumpxml-perl] libdata-dumpxml-perl: Removal of debhelper compat 4 Added tag(s) pending. > tag 465981 + pending Bug #465981 [libdata-dumpxml-perl] libdata-dumpxml-perl: should be arch:all Added tag(s)

Bug#817596: Pending fixes for bugs in the libdata-dumpxml-perl package

2016-12-16 Thread pkg-perl-maintainers
tag 817596 + pending tag 465981 + pending thanks Some bugs in the libdata-dumpxml-perl package are closed in revision b2645fa4732672f2f9dca5a5b0381177b7aedf11 in branch 'master' by Christoph Biedl The full diff can be seen at

Bug#844701: in package dpkg marked as pending

2016-12-16 Thread Guillem Jover
Control: tag 844701 pending Hi! Bug #844701 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=b51bc4f --- commit

Processed: Bug#844701 in package dpkg marked as pending

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tag 844701 pending Bug #844701 [dpkg] dpkg-maintscript-helper: Version comparison fails for supposedly valid versions Bug #846624 [dpkg] debconf: invalid version in maintainer script Added tag(s) pending. Added tag(s) pending. -- 844701:

Bug#846564: in package dpkg marked as pending

2016-12-16 Thread Guillem Jover
Control: tag 846564 pending Hi! Bug #846564 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/dpkg/dpkg.git/diff/?id=6801351 --- commit

Processed: Bug#846564 in package dpkg marked as pending

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tag 846564 pending Bug #846564 [dpkg] dpkg-deb: 'compressing tar member: lzma error: Cannot allocate memory' on 32-bit architectures on dpkg-deb -Zxz -Sextreme -z9 Added tag(s) pending. -- 846564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846564 Debian Bug

Bug#848139: CVE-2016-8707 ImageMagick Convert Tiff Adobe Deflate Code Execution Vulnerability

2016-12-16 Thread anarcat
Here's a patch for wheezy, which may be useful for jessie if, like wheezy, it lacks the ReadYCCKMethod case. From e5fd9ab1b70b2edd06de8efb606e04482cb9a2f0 Mon Sep 17 00:00:00 2001 From: Cristy Date: Thu, 1 Dec 2016 20:06:50 -0500 Subject: [PATCH] Fix possible

Bug#848197: marked as done (nvidia-graphics-drivers-legacy-304xx: CVE-2016-8826)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:04:19 + with message-id and subject line Bug#848197: fixed in nvidia-graphics-drivers-legacy-304xx 304.134-1 has caused the Debian Bug report #848197, regarding nvidia-graphics-drivers-legacy-304xx: CVE-2016-8826 to

Bug#845639: marked as done (Compatibility with xserver 1.19 / xorg-video-abi-23)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:04:18 + with message-id and subject line Bug#845639: fixed in nvidia-graphics-drivers-legacy-304xx 304.134-1 has caused the Debian Bug report #845639, regarding Compatibility with xserver 1.19 / xorg-video-abi-23 to

Bug#840342: [ace-of-penguins] Freecell No Longer Runs, Nvidia Legacy-304xx video driver

2016-12-16 Thread Andreas Beckmann
Hi, I just uploaded 304.134 to sid, it should appear on the mirrors later today. Please test it to see whether this bug is now fixed. Thanks Andreas

Processed: Bug#781457: ada bootstrap failure on mips and mipsel

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > found -1 6.2.1-6 Bug #781457 [gnat-6] ada bootstrap failure on mips and mipsel Marked as found in versions gcc-6/6.2.1-6. > severity -1 serious Bug #781457 [gnat-6] ada bootstrap failure on mips and mipsel Severity set to 'serious' from 'important' > tags -1 patch

Bug#847396: marked as done (ignition-math2 FTBFS: unit tests fail on all 32bit architectures)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Sat, 17 Dec 2016 01:56:27 +0100 with message-id and subject line Re: Bug#847396: ignition-math2 FTBFS: unit tests fail on all 32bit architectures has caused the Debian Bug report #847396, regarding

Processed: found 848195 in 343.22-1, found 848195 in 310.14-1, found 848195 in 173.14.05-1 ...

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 848195 343.22-1 Bug #848195 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2016-8826 Marked as found in versions nvidia-graphics-drivers/343.22-1. > found 848195 310.14-1 Bug #848195 [src:nvidia-graphics-drivers]

Processed: retitle 848384 for RC

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 848384 RFS: xmacro/0.3pre-2911-7 [RC] [ITA] Bug #848384 [sponsorship-requests] RFS: xmacro/0.3pre-2911-7 [ITA] Changed Bug title to 'RFS: xmacro/0.3pre-2911-7 [RC] [ITA]' from 'RFS: xmacro/0.3pre-2911-7 [ITA]'. > End of

Bug#848384: RFS: xmacro/0.3pre-20000911-7 [ITA]

2016-12-16 Thread Vincent Carluer
Package: sponsorship-requests Severity: serious Dear mentors, I am looking for a sponsor for my package "xmacro" * Package name: xmacro Version : 0.3pre-2911-7 Upstream Author : Gabor Keresztfalvi * URL :

Bug#800309: gkrellm-radio: diff for NMU version 2.0.4-1.2

2016-12-16 Thread Christoph Biedl
Control: tags 800309 + patch Control: tags 800309 + pending Control: tags 817339 + patch Control: tags 817339 + pending Dear maintainer, I've prepared an NMU for gkrellm-radio (versioned as 2.0.4-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer.

Processed: gkrellm-radio: diff for NMU version 2.0.4-1.2

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800309 + patch Bug #800309 [src:gkrellm-radio] gkrellm-radio: Please migrate a supported debhelper compat level Ignoring request to alter tags of bug #800309 to the same tags previously set > tags 800309 + pending Bug #800309 [src:gkrellm-radio] gkrellm-radio:

Bug#800297: gkrellm-mailwatch: diff for NMU version 2.4.3-1.1

2016-12-16 Thread Christoph Biedl
Control: tags 800297 + patch Control: tags 800297 + pending Dear maintainer, I've prepared an NMU for gkrellm-mailwatch (versioned as 2.4.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Christoph diff -u

Processed: gkrellm-mailwatch: diff for NMU version 2.4.3-1.1

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800297 + patch Bug #800297 [src:gkrellm-mailwatch] gkrellm-mailwatch: Please migrate a supported debhelper compat level Bug #817337 [src:gkrellm-mailwatch] gkrellm-mailwatch: Mandatory debian/compat for debhelper Ignoring request to alter tags of bug #800297

Processed: gkrellm-radio: diff for NMU version 2.0.4-1.2

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800309 + patch Bug #800309 [src:gkrellm-radio] gkrellm-radio: Please migrate a supported debhelper compat level Added tag(s) patch. > tags 800309 + pending Bug #800309 [src:gkrellm-radio] gkrellm-radio: Please migrate a supported debhelper compat level Added

Bug#800297: gkrellm-mailwatch: diff for NMU version 2.4.3-1.1

2016-12-16 Thread Christoph Biedl
Control: tags 800297 + patch Control: tags 800297 + pending Dear maintainer, I've prepared an NMU for gkrellm-mailwatch (versioned as 2.4.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards, Christoph diff -u

Processed: gkrellm-mailwatch: diff for NMU version 2.4.3-1.1

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800297 + patch Bug #800297 [src:gkrellm-mailwatch] gkrellm-mailwatch: Please migrate a supported debhelper compat level Bug #817337 [src:gkrellm-mailwatch] gkrellm-mailwatch: Mandatory debian/compat for debhelper Added tag(s) patch. Added tag(s) patch. > tags

Processed: Re: Bug#847812: pysolfc: crash on startup

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #847812 [pysolfc] pysolfc: crash on startup Severity set to 'grave' from 'normal' > tags -1 - unreproducible Bug #847812 [pysolfc] pysolfc: crash on startup Removed tag(s) unreproducible. -- 847812:

Bug#817359: marked as done (aspell-is: Removal of debhelper compat 4)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 23:04:20 + with message-id and subject line Bug#817359: fixed in aspell-is 0.51-0-utf8-0.1 has caused the Debian Bug report #817359, regarding aspell-is: Removal of debhelper compat 4 to be marked as done. This means

Bug#782720: marked as done (one filename is not valid utf-8)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 23:04:19 + with message-id and subject line Bug#782720: fixed in aspell-is 0.51-0-utf8-0.1 has caused the Debian Bug report #782720, regarding one filename is not valid utf-8 to be marked as done. This means that you

Processed: Re: Bug#848346: libnet-ssleay-perl: certificate verify fails

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libio-socket-ssl-perl Bug #848346 [libnet-ssleay-perl] libnet-ssleay-perl: certificate verify fails Bug reassigned from package 'libnet-ssleay-perl' to 'libio-socket-ssl-perl'. No longer marked as found in versions libnet-ssleay-perl/1.78-1. Ignoring

Bug#846799: Pending fixes for bugs in the golang-google-cloud package

2016-12-16 Thread Dmitry Smirnov
Hi Martín, On Friday, 16 December 2016 6:36:18 PM AEDT pkg-go- maintain...@lists.alioth.debian.org wrote: > The full diff can be seen at > https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/com > mit/?id=2262e13 > > Commit message: > > Ensure the transition from symlink

Bug#817362: marked as done (aspell-uz: Removal of debhelper compat 4)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 22:19:12 + with message-id and subject line Bug#817362: fixed in aspell-uz 0.6.0-2 has caused the Debian Bug report #817362, regarding aspell-uz: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#817355: marked as done (aspell-cy: Removal of debhelper compat 4)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 22:03:27 + with message-id and subject line Bug#817355: fixed in aspell-cy 0.50-3-6.1 has caused the Debian Bug report #817355, regarding aspell-cy: Removal of debhelper compat 4 to be marked as done. This means that

Bug#817357: marked as done (aspell-ga: Removal of debhelper compat 4)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 22:03:32 + with message-id and subject line Bug#817357: fixed in aspell-ga 0.50-4-4.1 has caused the Debian Bug report #817357, regarding aspell-ga: Removal of debhelper compat 4 to be marked as done. This means that

Bug#806629: marked as done (libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails))

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 22:04:18 + with message-id and subject line Bug#806629: fixed in libkarma 0.1.2-2.5 has caused the Debian Bug report #806629, regarding libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails) to be

Bug#817357: NMU of aspell-ga

2016-12-16 Thread Dr. Tobias Quathamer
Hi, I've just uploaded an NMU of aspell-ga, patch attached. Regards, Tobias diff -u aspell-ga-0.50-4/debian/changelog aspell-ga-0.50-4/debian/changelog --- aspell-ga-0.50-4/debian/changelog +++ aspell-ga-0.50-4/debian/changelog @@ -1,3 +1,10 @@ +aspell-ga (0.50-4-4.1) unstable; urgency=medium

Processed: Re: Bug#806629: libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch pending Bug #806629 [src:libkarma] libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails) Added tag(s) patch and pending. -- 806629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806629 Debian Bug Tracking System Contact

Bug#806629: libkarma: FTBFS when built with dpkg-buildpackage -A (dh_clideps fails)

2016-12-16 Thread Sébastien Villemot
Control: tags -1 + patch pending Dear Maintainer, Le dimanche 29 novembre 2015 à 16:22 +, Santiago Vila a écrit : > Package: src:libkarma > Version: 0.1.2-2.3 > User: sanv...@debian.org > Usertags: binary-indep > Severity: important > > Dear maintainer: > > I tried to build this package

Bug#828469: marked as done (openipmi: FTBFS with openssl 1.1.0)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 21:48:56 + with message-id and subject line Bug#828469: fixed in openipmi 2.0.22-1.1 has caused the Debian Bug report #828469, regarding openipmi: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim

Bug#817355: NMU of aspell-cy

2016-12-16 Thread Dr. Tobias Quathamer
Hi, I've just uploaded an NMU of aspell-cy, patch attached. Regards, Tobias diff -u aspell-cy-0.50-3/debian/changelog aspell-cy-0.50-3/debian/changelog --- aspell-cy-0.50-3/debian/changelog +++ aspell-cy-0.50-3/debian/changelog @@ -1,3 +1,10 @@ +aspell-cy (0.50-3-6.1) unstable; urgency=medium +

Bug#844633: coz-profiler: Cannot run build tests (insufficient permissions for perf)

2016-12-16 Thread Petter Reinholdtsen
Control: severity -1 important [Santiago Vila] > Based on the above comment, this bug should really be RC, because > Release Policy says that packages in stretch *must* be buildable in > stretch (this of course includes a machine running the default kernel > for stretch). All the dependencies

Processed: Re: coz-profiler: Cannot run build tests (insufficient permissions for perf)

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #844633 [coz-profiler] coz-profiler: Cannot run build tests (insufficient permissions for perf) Severity set to 'important' from 'serious' -- 844633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844633 Debian Bug Tracking System

Bug#845764: marked as done (cinnamon: polkit agent isn's set correctly)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 18:28:04 -0300 with message-id <20161216212803.GA21981@localhost> and subject line Closing this bug, the fix is already in unstable has caused the Debian Bug report #845764, regarding cinnamon: polkit agent isn's set correctly to be marked as done. This means

Bug#845357: marked as done ([nemo] Nemo does not open window after pressing "open as Root")

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 18:28:04 -0300 with message-id <20161216212803.GA21981@localhost> and subject line Closing this bug, the fix is already in unstable has caused the Debian Bug report #845764, regarding [nemo] Nemo does not open window after pressing "open as Root" to be marked as

Bug#845354: marked as done ([nemo] Nemo does not mounts partition)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 18:28:04 -0300 with message-id <20161216212803.GA21981@localhost> and subject line Closing this bug, the fix is already in unstable has caused the Debian Bug report #845764, regarding [nemo] Nemo does not mounts partition to be marked as done. This means that

Bug#846454: marked as done (verilator: add libfl-dev to Build-Depends)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 21:05:06 + with message-id and subject line Bug#846454: fixed in verilator 3.874-1.1 has caused the Debian Bug report #846454, regarding verilator: add libfl-dev to Build-Depends to be marked as done. This means that

Bug#800215: gkrellkam: diff for NMU version 2.0.0-1.2

2016-12-16 Thread Christoph Biedl
Control: tags 800215 + patch Control: tags 800215 + pending Control: tags 817335 + patch Control: tags 817335 + pending Dear maintainer, I've prepared an NMU for gkrellkam (versioned as 2.0.0-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards,

Processed: gkrellkam: diff for NMU version 2.0.0-1.2

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800215 + patch Bug #800215 [src:gkrellkam] gkrellkam: Please migrate a supported debhelper compat level Ignoring request to alter tags of bug #800215 to the same tags previously set > tags 800215 + pending Bug #800215 [src:gkrellkam] gkrellkam: Please migrate

Processed: gkrellkam: diff for NMU version 2.0.0-1.2

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800215 + patch Bug #800215 [src:gkrellkam] gkrellkam: Please migrate a supported debhelper compat level Added tag(s) patch. > tags 800215 + pending Bug #800215 [src:gkrellkam] gkrellkam: Please migrate a supported debhelper compat level Added tag(s) pending.

Bug#800308: gkrellmwireless: diff for NMU version 2.0.3-1.1

2016-12-16 Thread Christoph Biedl
Control: tags 800308 + patch Control: tags 800308 + pending Control: tags 817341 + patch Control: tags 817341 + pending Dear maintainer, I've prepared an NMU for gkrellmwireless (versioned as 2.0.3-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer.

Processed: gkrellmwireless: diff for NMU version 2.0.3-1.1

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800308 + patch Bug #800308 [src:gkrellmwireless] gkrellmwireless: Please migrate a supported debhelper compat level Added tag(s) patch. > tags 800308 + pending Bug #800308 [src:gkrellmwireless] gkrellmwireless: Please migrate a supported debhelper compat

Processed: gkrellmwireless: diff for NMU version 2.0.3-1.1

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 800308 + patch Bug #800308 [src:gkrellmwireless] gkrellmwireless: Please migrate a supported debhelper compat level Ignoring request to alter tags of bug #800308 to the same tags previously set > tags 800308 + pending Bug #800308 [src:gkrellmwireless]

Processed: gkrellm-leds: diff for NMU version 0.8.0-1.3

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 817336 + patch Bug #817336 [src:gkrellm-leds] gkrellm-leds: Mandatory debian/compat for debhelper Ignoring request to alter tags of bug #817336 to the same tags previously set > tags 817336 + pending Bug #817336 [src:gkrellm-leds] gkrellm-leds: Mandatory

Processed: gkrellm-leds: diff for NMU version 0.8.0-1.3

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > tags 817336 + patch Bug #817336 [src:gkrellm-leds] gkrellm-leds: Mandatory debian/compat for debhelper Added tag(s) patch. > tags 817336 + pending Bug #817336 [src:gkrellm-leds] gkrellm-leds: Mandatory debian/compat for debhelper Added tag(s) pending. > tags

Bug#817336: gkrellm-leds: diff for NMU version 0.8.0-1.3

2016-12-16 Thread Christoph Biedl
Control: tags 817336 + patch Control: tags 817336 + pending Control: tags 817476 + patch Control: tags 817476 + pending Dear maintainer, I've prepared an NMU for gkrellm-leds (versioned as 0.8.0-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards,

Bug#844633: coz-profiler: Cannot run build tests (insufficient permissions for perf)

2016-12-16 Thread Santiago Vila
Hi. If you absolutely need to run the tests during the build, maybe a workaround would be to add a build-depends on a package which changes the kernel value for you in its postinst (as I guess that the ordinary user used to build packages would not be able to do that). Yes, it would be a little

Processed: your mail

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 848349 + src:swift Bug #848349 [src:python-docutils] TypeError: unsupported operand type(s) for +=: int and str Added indication that 848349 affects src:swift > -- Stopping processing here. Please contact me if you need assistance. --

Processed: Re: coz-profiler: Cannot run build tests (insufficient permissions for perf)

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 844633 serious Bug #844633 [coz-profiler] coz-profiler: Cannot run build tests (insufficient permissions for perf) Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#846454: NMU of verilator

2016-12-16 Thread Dr. Tobias Quathamer
Hi, I've just uploaded an NMU with this simple fix, patch attached. Regards, Tobias diff --git a/debian/changelog b/debian/changelog index e94769c..21a259e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +verilator (3.874-1.1) unstable; urgency=medium + + * Non-maintainer

Bug#844479: RE:Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

2016-12-16 Thread PICCA Frederic-Emmanuel
Yes I work on this with the upstream :)) So don't worry I will tell you when it is ok. Cheers Fred

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

2016-12-16 Thread Dmitry Katsubo
On 2016-12-16 10:16, Alexander Alemayhu wrote: > On Thu, Dec 15, 2016 at 09:42:08PM +0100, Petter Reinholdtsen wrote: >> >> Personally I use tesseract these days for my OCR work, and do not need ocrad. > > I have unfortunately stopped using ocrad in favour of proprietary > solutions. > > Thanks

Bug#844479: RE:Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

2016-12-16 Thread Luca Boccassi
On Thu, 24 Nov 2016 09:58:33 + PICCA Frederic-Emmanuel wrote: > Hello, > > I just opened a bug for tango > > https://github.com/tango-controls/cppTango/issues/312 > > > what is the deadline where we can take the decision to upload or not

Bug#848131: marked as done (libmpich.so.12: cannot open shared object file: No such file or directory)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 19:20:21 + with message-id and subject line Bug#848131: fixed in tachyon 0.99~b6+dsx-7 has caused the Debian Bug report #848131, regarding libmpich.so.12: cannot open shared object file: No such file or directory to be

Bug#800215: About to prepare NMUs

2016-12-16 Thread Christoph Biedl
Hello, this is to let you know I will fix the packages Package: src:gkrellkam (debian/main). 800215 [] [U] gkrellkam: Please migrate a supported debhelper compat level 817335 [] [U] gkrellkam: Mandatory debian/compat for debhelper Package: src:gkrellm-leds

Bug#846799: marked as done (golang-google-cloud: fails to upgrade)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 18:49:08 + with message-id and subject line Bug#846799: fixed in golang-google-cloud 0.5.0-1 has caused the Debian Bug report #846799, regarding golang-google-cloud: fails to upgrade to be marked as done. This means

Bug#846322: marked as done (golang-google-cloud: FTBFS (undefined: grpc.SupportPackageIsVersion3))

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 18:49:08 + with message-id and subject line Bug#846322: fixed in golang-google-cloud 0.5.0-1 has caused the Debian Bug report #846322, regarding golang-google-cloud: FTBFS (undefined: grpc.SupportPackageIsVersion3) to be

Processed: Pending fixes for bugs in the golang-google-cloud package

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 846799 + pending Bug #846799 [src:golang-google-cloud] golang-google-cloud: fails to upgrade Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 846799:

Bug#846799: Pending fixes for bugs in the golang-google-cloud package

2016-12-16 Thread pkg-go-maintainers
tag 846799 + pending thanks Some bugs in the golang-google-cloud package are closed in revision 2262e13422c4bc67c492bc4bd5edf707ad676f47 in branch 'master' by Martín Ferrari The full diff can be seen at https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/commit/?id=2262e13

Bug#833754: xerces-c: FTBFS on s390x with gcc6/icu57

2016-12-16 Thread Bill Blough
I've prepared a new package and uploaded it to mentors: https://mentors.debian.net/debian/pool/main/x/xerces-c/xerces-c_3.1.4+debian-2.dsc If someone wants to test and/or upload it, I would appreciate it. Note: I didn't put an entry to close this bug because I intend to retitle it, lower the

Bug#848303: [Pkg-bitcoin-devel] Bug#848303: electrum: Transactions not accepted by network

2016-12-16 Thread s7r
You are using a version that produces transactions which have invalid signatures. Please upgrade to Electrum 2.7.12 by downloading it directly from https://electrum.org or using python pip. Thanks. The ports for Debian stable are not very compatible with the release cycle of Electrum wallet

Bug#848361: calendarserver: Regression in python-sqlparse 0.2.2-1 causes calendarserver fail at startup

2016-12-16 Thread P'tit g
Package: calendarserver Version: 7.0+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, Regression in python-sqlparse 0.2.2-1 causes calendarserver fail at startup -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990,

Processed: notfound 844820 in 2.6.0+dfsg1-3

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 844820 2.6.0+dfsg1-3 Bug #844820 {Done: wf...@niif.hu (Ferenc Wágner)} [src:shibboleth-sp2] shibboleth-sp2: FTBFS: unsatisfiable build-dependencies: libsaml2-dev (>= 2.5), libxmltooling-dev (>= 1.5) No longer marked as found in

Bug#844820: marked as done (shibboleth-sp2: FTBFS: unsatisfiable build-dependencies: libsaml2-dev (>= 2.5), libxmltooling-dev (>= 1.5))

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 17:39:05 +0100 with message-id <8737hnx1zq@lant.ki.iif.hu> and subject line Re: Bug#844820: shibboleth-sp2: FTBFS: unsatisfiable build-dependencies: libsaml2-dev (>= 2.5), libxmltooling-dev (>= 1.5) has caused the Debian Bug report #844820, regarding

Processed: notfound 844809 in 2.6.0-4

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 844809 2.6.0-4 Bug #844809 {Done: wf...@niif.hu (Ferenc Wágner)} [src:opensaml2] opensaml2: FTBFS: build-dependency not installable: libxmltooling-dev (>= 1.5) No longer marked as found in versions opensaml2/2.6.0-4. > thanks Stopping

Bug#844809: marked as done (opensaml2: FTBFS: build-dependency not installable: libxmltooling-dev (>= 1.5))

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 17:03:23 +0100 with message-id <877f6zx3n8@lant.ki.iif.hu> and subject line Re: Bug#844809: opensaml2: FTBFS: build-dependency not installable: libxmltooling-dev (>= 1.5) has caused the Debian Bug report #844809, regarding opensaml2: FTBFS: build-dependency

Bug#848162: (no subject)

2016-12-16 Thread Askar Safin
Moreover, this is regression. Jessie's konsole works well. Moreover, described behavior contradicts to konsole's documentation. I have konsole 4:16.08.2-2 . "konsole --help" says: -eCommand to execute. This option will catch all following

Processed: forwarded 848349

2016-12-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 848349 https://sourceforge.net/p/docutils/bugs/303/ Bug #848349 [src:python-docutils] TypeError: unsupported operand type(s) for +=: int and str Set Bug forwarded-to-address to 'https://sourceforge.net/p/docutils/bugs/303/'. > kthxbye

Bug#828527: marked as done (radsecproxy: FTBFS with openssl 1.1.0)

2016-12-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Dec 2016 15:22:57 + with message-id and subject line Bug#828527: fixed in radsecproxy 1.6.8-1 has caused the Debian Bug report #828527, regarding radsecproxy: FTBFS with openssl 1.1.0 to be marked as done. This means that you

Bug#844701: dpkg-maintscript-helper: Version comparison fails for supposedly valid versions

2016-12-16 Thread Guillem Jover
On Fri, 2016-12-16 at 14:32:35 +0100, Guido Günther wrote: > On Fri, Dec 16, 2016 at 02:17:05PM +0100, Guillem Jover wrote: > > […] Which is what I'm > > in principle planning on merging for .16 which I should really be > > releasing this week. :/ > > > > Sorry for the delay. Things have not been

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Michael Kerrisk (man-pages)
Hello Thorsten, On 12/16/2016 03:36 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> On 12/16/2016 02:53 PM, Thorsten Glaser wrote: >>> On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: >>> That doesn't document (upstream) reality though. Once

Bug#848351: netdata: FTBFS: cannot create .../netdata-data/...

2016-12-16 Thread Aaron M. Ucko
Source: netdata Version: 1.3.0+dfsg-1 Severity: serious Justification: fails to build from source Builds of netdata covering only its architecture-dependent binary package (as on the autobuilders, or with dpkg-buildpackage -B) have been failing: echo 0 >

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Thorsten Glaser
On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > On 12/16/2016 02:53 PM, Thorsten Glaser wrote: > > On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > > > >> That doesn't document (upstream) reality though. Once upon a time, > >> there were one or two Section 9 pages in the

Processed: TypeError: unsupported operand type(s) for +=: int and str

2016-12-16 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:linux Bug #848349 [src:python-docutils] TypeError: unsupported operand type(s) for +=: int and str Added indication that 848349 affects src:linux -- 848349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848349 Debian Bug Tracking System

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Michael Kerrisk (man-pages)
On 12/16/2016 02:53 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > >> That doesn't document (upstream) reality though. Once upon a time, >> there were one or two Section 9 pages in the man-pages >> project. No one updated them or added new one in > 15

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Thorsten Glaser
On Fri, 16 Dec 2016, Michael Kerrisk (man-pages) wrote: > That doesn't document (upstream) reality though. Once upon a time, > there were one or two Section 9 pages in the man-pages > project. No one updated them or added new one in > 15 years, > and I deleted them years ago, as being out-of-date

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Michael Kerrisk (man-pages)
On 12/16/2016 02:37 PM, Axel Beckert wrote: > Hi, > > Thorsten Glaser wrote: >> On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: >>> Upstream man-pages maintainer here; I just added tmpfs(5), unaware >>> that it would create a conflict for Debian; I assume the conflicting >>> page is

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Michael Kerrisk (man-pages)
On 12/16/2016 02:40 PM, Thorsten Glaser wrote: > On Fri, 16 Dec 2016, Axel Beckert wrote: > > The manpage about the Linux tmpfs should be tmpfs(9) as it > covers a kernel concept (here: a filesystem). Not sure where this idea originates. There is no Section 9 on Linux. >>> >>>

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Thorsten Glaser
On Fri, 16 Dec 2016, Axel Beckert wrote: > > > > The manpage about the Linux tmpfs should be tmpfs(9) as it > > > > covers a kernel concept (here: a filesystem). > > > > > > Not sure where this idea originates. There is no Section 9 on Linux. > > > > Ah, hmm, too bad then. We have them on BSD.

Bug#847998: [Pkg-sysvinit-devel] Bug#847998: manpages: file conflicts with initscripts

2016-12-16 Thread Axel Beckert
Hi, Thorsten Glaser wrote: > On Tue, 13 Dec 2016, Michael Kerrisk (man-pages) wrote: > > Upstream man-pages maintainer here; I just added tmpfs(5), unaware > > that it would create a conflict for Debian; I assume the conflicting > > page is Debian-specific(?). (I don't have such a page on my

Bug#844701: dpkg-maintscript-helper: Version comparison fails for supposedly valid versions

2016-12-16 Thread Guido Günther
On Fri, Dec 16, 2016 at 02:17:05PM +0100, Guillem Jover wrote: > Hi! > > On Fri, 2016-12-16 at 11:00:01 +0100, Guido Günther wrote: > > I've tried the attached patches they still fail in my use case (pbuilder > > create). The reason is that stderr contains completely unrelated garbish > > form

Bug#847526: stimfit FTBFS on architectures where char is unsigned.

2016-12-16 Thread Christoph Schmidt-Hieber
Hi, Just a quick reminder that a Debian Developer (Yaro?) will have to upload the package from https://mentors.debian.net/package/stimfit for this bug to get fixed. Christoph On Sat, Dec 10, 2016 at 06:16:23PM +0100, Christoph Schmidt-Hieber wrote: > Thanks for the bug report. > > Fixed in

Bug#825084: Package links against libmysqlclient_r

2016-12-16 Thread Lars Tangvald
Hi, There isn't really a way to verify the thread safety aside from what's in the test suite, but how old systems do you consider when you say «old boxes»? Ones with eol'ed versions of MySQL (< 5.5)? In 5.5 and 5.6 there's no difference between libmysqlclient and libmysqlclient_r, as the

Bug#844701: dpkg-maintscript-helper: Version comparison fails for supposedly valid versions

2016-12-16 Thread Guillem Jover
Hi! On Fri, 2016-12-16 at 11:00:01 +0100, Guido Günther wrote: > I've tried the attached patches they still fail in my use case (pbuilder > create). The reason is that stderr contains completely unrelated garbish > form ld.so. I've added a version that relies on exit status only. Can > this be

  1   2   >