Bug#813949: bluetooth: error causing service to be unusable: Not enough free handles to register service

Control: severity -1 normal Control: severity 815146 normal Hello! > Try enabling experimental features from bluetoothd : > (...) > This fixed the : > (...) So, basically the bluetooth package works as expected and there is no actual bug that justifies the severity 'grave' as per Debian Policy,

Processed: Re: bluetooth: error causing service to be unusable: Not enough free handles to register service

Processing control commands: > severity -1 normal Bug #813949 [bluetooth] bluetooth: error causing service to be unusable: Not enough free handles to register service Bug #815146 [bluetooth] bluetooth: Can't start bluetoothd service cause «not enough free handles to register service» Severity

Bug#856004: khtml: please build-depen on libssl1.0-dev for Stretch

On 03/01/2017 08:21 AM, Sebastian Andrzej Siewior wrote: >> The problem is that if the package was to be rebuilt now, it would be >> rebuilt with OpenSSL 1.1 and not OpenSSL 1.0 which is the original >> motivation for this bug report by Sebastian! > > it already has been built with 1.1. We are

Processed: severity of 856774 is serious

Processing commands for cont...@bugs.debian.org: > # breaks the package > severity 856774 serious Bug #856774 [xfce4-equake-plugin] xfce4-equake-plugin: Fails to download data, needs to use https Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if

Bug#855282: debsign: support .buildinfo files

On Thu, Feb 16, 2017 at 05:23:00PM +, Ximin Luo wrote: > I've done an initial implementation here: > > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo > > Please review! This was merged and uploaded in 2.17.2. However, now I see that buildinfo files

Bug#855872: marked as done (command line arguments are not properly handled (breaking existing applications))

Your message dated Tue, 07 Mar 2017 03:20:43 + with message-id and subject line Bug#855872: fixed in icedove 1:45.7.1-2 has caused the Debian Bug report #855872, regarding command line arguments are not properly handled (breaking existing applications) to

Bug#855343: marked as done (thunderbird: AppArmor profile contains faulty characters (Syntax Error))

Your message dated Tue, 07 Mar 2017 03:20:43 + with message-id and subject line Bug#855343: fixed in icedove 1:45.7.1-2 has caused the Debian Bug report #855343, regarding thunderbird: AppArmor profile contains faulty characters (Syntax Error) to be

Bug#854587: marked as done (icedove: incorrect start-version in {icedove,thunderbird}.maintscript)

Your message dated Tue, 07 Mar 2017 03:20:43 + with message-id and subject line Bug#854587: fixed in icedove 1:45.7.1-2 has caused the Debian Bug report #854587, regarding icedove: incorrect start-version in {icedove,thunderbird}.maintscript to be marked

Bug#854701: python-asyncssh: FTBFS (failing tests)

Hello Santiago, are you still able to reproduce this in your environment? i just tried on an up-to-date pbuilder chroot and it built fine (it was running in a X environment tho). On Thu, 09 Feb 2017 16:14:13 + Santiago Vila wrote: > Package: src:python-asyncssh > Version:

Bug#856925: marked as done (systray-mdstat: fails to start: Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156.)

Your message dated Mon, 06 Mar 2017 23:18:54 + with message-id and subject line Bug#856925: fixed in systray-mdstat 1.0.1-1 has caused the Debian Bug report #856925, regarding systray-mdstat: fails to start: Icon harddriveok.png not found at

Bug#856705: closed by Ruben Undheim <ruben.undh...@gmail.com> (Bug#856705: fixed in graywolf 0.1.4+20170306gitecee764-1)

Debian Bug Tracking System writes: > This is an automatic notification regarding your Bug report > which was filed against the src:graywolf package: > > #856705: graywolf: License violation > > It has been closed by Ruben Undheim . Thanks for

Bug#856983: tigris: Incomplete debian/copyright?

Apollon Oikonomopoulos wrote: > Thanks for the heads up. This file is used as input text for the tests. > Apparently it's the Wikipedia page on the Danish philosopher Søren > Kierkegaard. As all Wikipedia pages, it's licensed under CC-BY-SA 3.0. Great to hear; don't forget, its more for our

Bug#856983: Pending fixes for bugs in the tigris package

tag 856983 + pending thanks Some bugs in the tigris package are closed in revision e205ae0f9d2ba8b4045da73193b2faf78427fa6f in branch 'master' by Apollon Oikonomopoulos The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/tigris.git/commit/?id=e205ae0 Commit message:

Processed: Pending fixes for bugs in the tigris package

Processing commands for cont...@bugs.debian.org: > tag 856983 + pending Bug #856983 [src:tigris] tigris: Incomplete debian/copyright? Warning: Unknown package 'src:tigris' Added tag(s) pending. Warning: Unknown package 'src:tigris' > thanks Stopping processing here. Please contact me if you need

Bug#856983: tigris: Incomplete debian/copyright?

Hi Chris, On 21:40 Mon 06 Mar , Chris Lamb wrote: > Source: tigris > Version: 0.1.1-1 > Severity: serious > Justication: Policy 12.5 > X-Debbugs-CC: Apollon Oikonomopoulos > > Hi, > > I just ACCEPTed tigris from NEW but noticed it was missing > attribution or

Bug#855576: marked as done (openstack-dashboard: fails to install: django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 'openstack_auth.User' that has not been installed)

Your message dated Mon, 6 Mar 2017 23:00:10 +0100 with message-id and subject line Re: [PKG-Openstack-devel] horizon is marked for autoremoval from testing has caused the Debian Bug report #855576, regarding openstack-dashboard: fails to install:

Bug#856705: marked as done (graywolf: License violation)

Your message dated Mon, 06 Mar 2017 21:48:56 + with message-id and subject line Bug#856705: fixed in graywolf 0.1.4+20170306gitecee764-1 has caused the Debian Bug report #856705, regarding graywolf: License violation to be marked as done. This means that

Bug#856983: tigris: Incomplete debian/copyright?

Source: tigris Version: 0.1.1-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Apollon Oikonomopoulos Hi, I just ACCEPTed tigris from NEW but noticed it was missing attribution or clarification in debian/copyright for the large-string.txt file. Please could you

Bug#811806: Patch file for bug #811806

Hello, in addition to my previous message, please find enclosed a clean patch file generated with quilt. Could you please update the package in order to let it migrate to testing distribution? Thanks, François--- a/effects/ppeffect.cpp +++ b/effects/ppeffect.cpp @@ -113,7 +113,7 @@ {

Bug#856937: marked as done (libslvs1-dev: missing Depends: libslvs1 (= ${binary:Version}))

Your message dated Mon, 06 Mar 2017 21:05:32 + with message-id and subject line Bug#856937: fixed in solvespace 2.3+repack1-2 has caused the Debian Bug report #856937, regarding libslvs1-dev: missing Depends: libslvs1 (= ${binary:Version}) to be marked as

Processed: tagging 856925

Processing commands for cont...@bugs.debian.org: > tags 856925 + pending Bug #856925 [systray-mdstat] systray-mdstat: fails to start: Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 856925

Processing commands for cont...@bugs.debian.org: > tags 856925 + confirmed Bug #856925 [systray-mdstat] systray-mdstat: fails to start: Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156. Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need

Bug#856834: [pkg-go] Bug#856834: tendermint-go-rpc: FTBFS: panic: Failed to listen to unix:///tmp/go-rpc.sock: listen unix /tmp/go-rpc.sock: bind: address already in use

On Mon, Mar 6, 2017 at 10:36 AM, Jack Henschel wrote: > Would be great if someone uploaded the (fixed) package. Uploading it right now, thanks! -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer

Processed: Re: kmldonkey: Segfault starting

Processing control commands: > tags -1 unreproducible Bug #856948 [kmldonkey] kmldonkey: Segfault starting Added tag(s) unreproducible. > tags -1 moreinfo Bug #856948 [kmldonkey] kmldonkey: Segfault starting Added tag(s) moreinfo. -- 856948:

Bug#856948: kmldonkey: Segfault starting

Control: tags -1 unreproducible Control: tags -1 moreinfo Hi Francesco! > After latest updates in kdelibs and qtlibs whem starting kmldonkey it goes > segfault. > I'll attach a kcrash generated file for debugging, if it can be useful. I just tried to reproduce your problem but after installing

Bug#850114: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

Control: tags -1 patch Hi! The attached debdiff contains a patch which fixes the issue. It turns out that someone, for whatever reasons, had hard-coded the disc ID to "64e.YDM.N2tZJzmqrN48iWfJ9.4-" [1] which is the ID for Nirvana's "Smells Like Teen Spirit" album. Just reverting the patch fixes

Processed: Re: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

Processing control commands: > tags -1 patch Bug #850114 [kscd] kscd: Retrieved CD information is always incorrect Added tag(s) patch. -- 850114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

Processing control commands: > retitle -1 kscd: Retrieved CD information is always incorrect Bug #850114 [kscd] kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode) Changed Bug title to 'kscd: Retrieved CD information is always incorrect' from

Bug#850114: kscd: Only play first trackon all modes(loop track, loop ,and no loop and random and no random mode)

Control: retitle -1 kscd: Retrieved CD information is always incorrect Hi Pere! I finally had the chance to look at this bug and test it myself, it took me a bit longer because my laptop doesn't have a CD-ROM drive and I had to hook up an external USB drive. I tried to reproduce the problem you

Bug#856881: Not found in stable and oldstable

control: notfound - 1 8:6.8.9.9-5+deb8u7 control: notfound - 1 8:6.7.7.10-5+deb7u11 code is not present

Bug#856882: Fwd: Not found in stable and oldstable

control: notfound - 1 8:6.8.9.9-5+deb8u7 control: notfound - 1 8:6.7.7.10-5+deb7u11 code is not present

Bug#856826: Acknowledgement (installation-reports: Debian 8.6 installer with encrypted swap creates unusable swap logical volume)

Hello, This can be closed, it looks like there was some kind of problem with the netinstall disk my host was using, as if I use my own, everything works fine. Thanks! On 05/03/17 14:54, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > This is an

Processed: 845323 is RC

Processing commands for cont...@bugs.debian.org: > severity 845323 serious Bug #845323 [ovirt-guest-agent] ovirt-guest-agent: Ovirt-guest-agent crashes with a stack smash Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#856949: libgiac-dev: missing Depends: libgiac0 (= ${binary:Version})

Package: libgiac-dev Version: 1.2.3.25+dfsg1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m26.1s ERROR: FAIL: Broken

Bug#856948: kmldonkey: Segfault starting

Package: kmldonkey Version: 2.0.5+kde4.3.3-3+b1 Severity: grave Justification: renders package unusable Dear Maintainer, After latest updates in kdelibs and qtlibs whem starting kmldonkey it goes segfault. I'll attach a kcrash generated file for debugging, if it can be useful. -- System

Bug#856947: libgxw*-dev: broken symlink: /usr/lib/libgxw*.so -> /build/guitarix-WlZ7JB/guitarix-0.35.2/debian/tmp/usr/lib/libgxw*.so.0.1

Package: libgxwmm-dev,libgxw-dev Version: 0.35.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m34.7s ERROR: FAIL: Broken

Bug#856946: libdmraid-dev: broken symlink: /usr/lib/libdmraid.so -> /lib/libdmraid.so.1.0.0.rc15

Package: libdmraid-dev Version: 1.0.0.rc16-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m18.0s ERROR: FAIL: Broken symlinks:

Processed: rekall: package not installable after no-change rebuild

Processing commands for cont...@bugs.debian.org: > affects 856926 Bug #856926 [dh-python,rekall] rekall: package not installable after no-change rebuild Removed indication that 856926 affects dh-python > reassign 856926 rekall Bug #856926 [dh-python,rekall] rekall: package not installable after

Bug#856945: libsnapper-dev: missing Depends: libsnapper4 (= ${binary:Version})

Package: libsnapper-dev Version: 0.4.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m16.5s ERROR: FAIL: Broken symlinks:

Bug#856937: libslvs1-dev: missing Depends: libslvs1 (= ${binary:Version})

Package: libslvs1-dev Version: 2.3+repack1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m21.2s ERROR: FAIL: Broken symlinks:

Bug#856936: quagga: libquagga0 contains libraries with different SOVERSIONS

Source: quagga Version: 1.1.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed libquagga-dev contains a a broken symlink: /usr/lib/x86_64-linux-gnu/libzebra.so -> libzebra.so.0 because libquagga0 ships the following files:

Bug#855888: The following patch for libidn2 is more appropriate and the bug should be redirected to libidn2

On 03/06/2017 01:26 PM, Eric Valette wrote: Hi, I tested the following patch successfully: https://gitweb.gentoo.org/repo/gentoo.git/patch/?id=31d5415bc400feba9b5f82354aa1667a81f831ea -- eric Looking at gitlab, the patch has been applied upstream. -- eric

Processed: bug 854701 is forwarded to https://github.com/ronf/asyncssh/issues/81

Processing commands for cont...@bugs.debian.org: > forwarded 854701 https://github.com/ronf/asyncssh/issues/81 Bug #854701 [src:python-asyncssh] python-asyncssh: FTBFS (failing tests) Set Bug forwarded-to-address to 'https://github.com/ronf/asyncssh/issues/81'. > thanks Stopping processing here.

Bug#855888: The following patch for libidn2 is more appropriate and the bug should be redirected to libidn2

Hi, I tested the following patch successfully: https://gitweb.gentoo.org/repo/gentoo.git/patch/?id=31d5415bc400feba9b5f82354aa1667a81f831ea -- eric

Bug#856926: Processed: rekall: package not installable after no-change rebuild

rekall's setup.py contains¹ (in install_requires): "pycrypto == 2.6.1" which is translated by dh_python2 into "python-crypto (= 2.6.1)" (translating == into = and not simply ignoring it, or replacing with ">=" which is IMO the least problematic solution, is a new thing introduced in dh-python

Bug#856879: marked as done (CVE-2017-6500: sun file heap-based buffer over-read)

Your message dated Mon, 06 Mar 2017 12:05:45 + with message-id and subject line Bug#856879: fixed in imagemagick 8:6.9.7.4+dfsg-2 has caused the Debian Bug report #856879, regarding CVE-2017-6500: sun file heap-based buffer over-read to be marked as done.

Bug#856881: marked as done (CVE-2017-6501: null pointer deref in xcf coder)

Your message dated Mon, 06 Mar 2017 12:05:45 + with message-id and subject line Bug#856881: fixed in imagemagick 8:6.9.7.4+dfsg-2 has caused the Debian Bug report #856881, regarding CVE-2017-6501: null pointer deref in xcf coder to be marked as done. This

Bug#856880: marked as done (CVE-2017-6499: Magick++ memory leak)

Your message dated Mon, 06 Mar 2017 12:05:45 + with message-id and subject line Bug#856880: fixed in imagemagick 8:6.9.7.4+dfsg-2 has caused the Debian Bug report #856880, regarding CVE-2017-6499: Magick++ memory leak to be marked as done. This means that

Bug#856882: marked as done ([CVE-2017-6497] Added missing null check in psd coder)

Your message dated Mon, 06 Mar 2017 12:05:45 + with message-id and subject line Bug#856882: fixed in imagemagick 8:6.9.7.4+dfsg-2 has caused the Debian Bug report #856882, regarding [CVE-2017-6497] Added missing null check in psd coder to be marked as

Bug#856878: marked as done (CVE-2017-6498: TGA files could trigger assertion failures)

Your message dated Mon, 06 Mar 2017 12:05:45 + with message-id and subject line Bug#856878: fixed in imagemagick 8:6.9.7.4+dfsg-2 has caused the Debian Bug report #856878, regarding CVE-2017-6498: TGA files could trigger assertion failures to be marked as

Bug#856536: [Packaging] Bug#856536: munin: regression from DSA-3794-2: spams munin logs with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in string eq at /usr/lib/munin/cgi/

Hi Jonas, hi Salvatore, could you please be so kind and push your wheezy and jessie uploads to munin.git too? It's lives in collab-maint on alioth, so you both should have write access already :) Please just push it as signed tags (based on previous tags), not as branches, and please use the

Processed: rekall: package not installable after no-change rebuild

Processing commands for cont...@bugs.debian.org: > found 856926 rekall/1.6.0+dfsg-1 Bug #856926 [dh-python,rekall] rekall: package not installable after no-change rebuild Marked as found in versions rekall/1.6.0+dfsg-1. > found 856926 dh-python/2.20170125 Bug #856926 [dh-python,rekall] rekall:

Bug#694308: forwarded

control: forwarded -1 https://github.com/adobe-type-tools/afdko/issues/172

Processed: forwarded

Processing control commands: > forwarded -1 https://github.com/adobe-type-tools/afdko/issues/172 Bug #694308 [general] A lot of type 1 fonts include Adobe all right reserved code Set Bug forwarded-to-address to 'https://github.com/adobe-type-tools/afdko/issues/172'. -- 694308:

Bug#817236: schroot: no access to pseudo-terminals in new chroots

On Sun, 05 Mar 2017 at 19:41:14 +, Simon McVittie wrote: > I have filed #856877 against schroot suggesting mounting a new instance > of /dev/pts, effectively making schroot behave less like chroot and more > like a container manager in this particular respect. > > However, that causes a nasty

Processed: rekall: package not installable after no-change rebuild

Processing commands for cont...@bugs.debian.org: > reassign 856926 dh-python, rekall Bug #856926 [src:rekall] rekall: package not installable after no-change rebuild Bug reassigned from package 'src:rekall' to 'dh-python,rekall'. No longer marked as found in versions dh-python/2.20170125 and

Processed: rekall: package not installable after no-change rebuild

Processing commands for cont...@bugs.debian.org: > affects 856926 dh-python Bug #856926 [src:rekall] rekall: package not installable after no-change rebuild Added indication that 856926 affects dh-python > thanks Stopping processing here. Please contact me if you need assistance. -- 856926:

Processed: rekall: package not installable after no-change rebuild

Processing commands for cont...@bugs.debian.org: > found 856926 dh-python/2.20170125 Bug #856926 [src:rekall] rekall: package not installable after no-change rebuild Marked as found in versions dh-python/2.20170125. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#835692: marked as done (gcc-5-cross-ports: FTBFS: patches fail to apply)

Your message dated Mon, 06 Mar 2017 11:03:58 + with message-id and subject line Bug#835692: fixed in gcc-5-cross-ports 11 has caused the Debian Bug report #835692, regarding gcc-5-cross-ports: FTBFS: patches fail to apply to be marked as done. This means

Bug#856925: systray-mdstat: fails to start: Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156.

Hi Damian, thanks for the bug report. Happy to see that the tool might be interesting for others, too. :-) Damyan Ivanov wrote: > % systray-mdstat > Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156. Hrm. I know I worked on this as one of the last things before releasing it.

Bug#856926: rekall: package not installable after no-change rebuild

Source: rekall Version: 1.6.0+dfsg-1 Severity: serious Hi Maintainer Rebuilding rekall in sid or testing results in package python-rekall-core not being installable due to a strict versioned dependency on python-crypto (= 2.6.1). See contents of python-rekall-core.substvars:

Bug#856925: systray-mdstat: fails to start: Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156.

Package: systray-mdstat Version: 1.0.0-1 Severity: grave Tags: patch Trying to start systray-mdstat fails with: % systray-mdstat Icon harddriveok.png not found at /usr/bin/systray-mdstat line 156. strace shows three failed attempts to open the file: % strace -e trace=file systray-mdstat

Processed: Re: Bug#856834: tendermint-go-rpc: FTBFS: panic: Failed to listen to unix:///tmp/go-rpc.sock: listen unix /tmp/go-rpc.sock: bind: address already in use

Processing control commands: > tag -1 +patch Bug #856834 [src:tendermint-go-rpc] tendermint-go-rpc: FTBFS: panic: Failed to listen to unix:///tmp/go-rpc.sock: listen unix /tmp/go-rpc.sock: bind: address already in use Added tag(s) patch. -- 856834:

Bug#856834: tendermint-go-rpc: FTBFS: panic: Failed to listen to unix:///tmp/go-rpc.sock: listen unix /tmp/go-rpc.sock: bind: address already in use

Control: tag -1 +patch This problematic is actually documented in the code: rpc_test.go > var ( >tcpAddr = "tcp://0.0.0.0:46657" >unixAddr = "unix:///tmp/go-rpc.sock" // NOTE: must remove file for > test to run again >websocketEndpoint = "/websocket/endpoint" > ) Patch

Processed: retitle

Processing control commands: > tag -1 + patch Bug #856881 [src:imagemagick] [src:imagemagick] Avoid null pointer dereference in xcf coder Ignoring request to alter tags of bug #856881 to the same tags previously set > retitle -1 CVE-2017-6501: null pointer deref in xcf coder Bug #856881

Bug#856881: retitle

control: tag -1 + patch control: retitle -1 CVE-2017-6501: null pointer deref in xcf coder

Processed: tagging 856882

Processing commands for cont...@bugs.debian.org: > tags 856882 + patch Bug #856882 [src:imagemagick] [CVE-2017-6497] Added missing null check in psd coder Ignoring request to alter tags of bug #856882 to the same tags previously set > thanks Stopping processing here. Please contact me if you

Processed: tagging 856881

Processing commands for cont...@bugs.debian.org: > tags 856881 + patch Bug #856881 [src:imagemagick] [src:imagemagick] Avoid null pointer dereference in xcf coder Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 856881:

Bug#856880: retitle

control: tag -1 + patch control: retitle -1 CVE-2017-6499: Magick++ memory leak

Processed: retitle

Processing control commands: > tag -1 + patch Bug #856880 [src:imagemagick] [src:imagemagick] Fixed memory leak when creating nested exceptions in Magick++ Added tag(s) patch. > retitle -1 CVE-2017-6499: Magick++ memory leak Bug #856880 [src:imagemagick] [src:imagemagick] Fixed memory leak

Processed: tagging 856879

Processing commands for cont...@bugs.debian.org: > tags 856879 + patch Bug #856879 [src:imagemagick] CVE-2017-6500: sun file heap-based buffer over-read Ignoring request to alter tags of bug #856879 to the same tags previously set > thanks Stopping processing here. Please contact me if you need

Bug#856879: retitle

control: tag -1 + patch control: retitle -1 CVE-2017-6500: sun file heap-based buffer over-read

Processed: retitle

Processing control commands: > tag -1 + patch Bug #856879 [src:imagemagick] [src:imagemagick] out-of-bounds read Added tag(s) patch. > retitle -1 CVE-2017-6500: sun file heap-based buffer over-read Bug #856879 [src:imagemagick] [src:imagemagick] out-of-bounds read Changed Bug title to

Processed: tagging 856878

Processing commands for cont...@bugs.debian.org: > tags 856878 + patch Bug #856878 [src:imagemagick] CVE-2017-6498: TGA files could trigger assertion failures Ignoring request to alter tags of bug #856878 to the same tags previously set > thanks Stopping processing here. Please contact me if

Processed: tagging 856880

Processing commands for cont...@bugs.debian.org: > tags 856880 + patch Bug #856880 [src:imagemagick] CVE-2017-6499: Magick++ memory leak Ignoring request to alter tags of bug #856880 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: retitle

Processing control commands: > tags -1 + patch Bug #856878 [src:imagemagick] [src:imagemagick] Assertion failure in TGA coder Added tag(s) patch. > retitle -1 CVE-2017-6498: TGA files could trigger assertion failures Bug #856878 [src:imagemagick] [src:imagemagick] Assertion failure in TGA coder

Bug#856882: retitle

control: tags -1 + patch control: retitle -1 [CVE-2017-6497] Added missing null check in psd coder

Processed: retitle

Processing control commands: > tags -1 + patch Bug #856882 [src:imagemagick] [src:imagemagick] Added missing null check in psd coder Added tag(s) patch. > retitle -1 [CVE-2017-6497] Added missing null check in psd coder Bug #856882 [src:imagemagick] [src:imagemagick] Added missing null check

Bug#856878: retitle

control: tags -1 + patch control: retitle -1 CVE-2017-6498: TGA files could trigger assertion failures

Bug#856878: Multiple imagemagick RC bugs

Hi Bastien! Since all these aforementioned issues have already a patch available, these bug reports should be tagged as "patch" so they don't show up in the list of RC bugs anymore for which a patch doesn't exist yet [1]. This reduces the noise on the list and helps anyone who wants to work on

Processed: merge GCC issues

Processing commands for cont...@bugs.debian.org: > forcemerge 845751 856809 Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Bug #845751 [gcc-6] yadifa FTBFS on ppc64el: internal compiler error: in push_reload, at reload.c:1349 Marked as

Bug#856904: ksirk FTBFS on architectures where char is unsigned

Control: tags -1 patch Hi! The attached debdiff contains a trivial patch which changes the declaration of tbl[] from "char" to "signed char". With the patch applied, I verified that the package builds successfully on armhf. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian

Processed: Re: ksirk FTBFS on architectures where char is unsigned

Processing control commands: > tags -1 patch Bug #856904 [src:ksirk] ksirk FTBFS on architectures where char is unsigned Added tag(s) patch. -- 856904: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#856039: xserver-xorg-core: no keyboard and no mouse

Hi folks, sorry for the late reply... On Mon, Feb 27, 2017 at 06:17:42PM +0900, Michel Dänzer wrote: > The client side has no impact on which drivers Xorg loads, or when. It > looks like simply neither xserver-xorg-input-libinput nor > xserver-xorg-input-evdev is installed. the problem turned

Processed: mark issue as pending

Processing commands for cont...@bugs.debian.org: > tags 856903 + pending Bug #856903 [gcj-6] gcj-6: Broken ecj1 symlink on i386 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 856903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856903