Processed: severity of 751933 is important

Processing commands for cont...@bugs.debian.org: > severity 751933 important Bug #751933 [cachefilesd] cachefilesd: Under heavy NFS load the machine will hang hard Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 751933:

Bug#811956: marked as done (FTBFS: error: expected '='...)

Your message dated Fri, 25 Mar 2016 04:49:49 + with message-id and subject line Bug#811956: fixed in ucblogo 5.5-3 has caused the Debian Bug report #811956, regarding FTBFS: error: expected '='... to be marked as done. This means that you claim that the

Bug#816517: marked as done (FTBFS: /usr/bin/mktexfmt: mkdir(/sbuild-nonexistent/))

Your message dated Fri, 25 Mar 2016 05:03:31 +0100 with message-id <20160325040331.ga29...@angband.pl> and subject line builds fine now has caused the Debian Bug report #816517, regarding FTBFS: /usr/bin/mktexfmt: mkdir(/sbuild-nonexistent/) to be marked as done. This means that you claim that

Bug#815173: Info received (kernel-image-4.4.0-1-amd64 does not boot)

I'm on version 4.4.6-1 On Thu, Mar 24, 2016 at 8:03 PM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been

Bug#819214: golang-ginkgo: FTBFS: dh_auto_test: go test -v [..] returned exit code 1

Source: golang-ginkgo Version: 1.2.0-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-ginkgo fails to build from source in

Bug#819216: ruby-numru-misc: FTBFS: `load_gemspec': E: cannot load gemspec numru-misc.gemspec (RuntimeError)

Source: ruby-numru-misc Version: 0.1.2-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-numru-misc fails to build from source in

Bug#819215: golang-github-aws-aws-sdk-go: FTBFS: rename.go:92: impossible type switch case: v (type "go/types".Object) cannot have dynamic type

Source: golang-github-aws-aws-sdk-go Version: 1.0.7+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-github-aws-aws-sdk-go fails

Bug#815173: kernel-image-4.4.0-1-amd64 does not boot

Referring to issue #815173 which has been marked as fixed. I am experiencing exact same issue as reported by the OP on Feb 16. Current kernels installed 4.3.0.1 (no problems) and 4.4.0.1 - the boot dies very early on, no logs in syslog / dmesg. However, it generated a bunch of *efivars dump

Bug#818420: marked as done (ices2: FTBFS: required file `./depcomp' not found)

Your message dated Thu, 24 Mar 2016 23:54:47 + with message-id and subject line Bug#818420: fixed in ices2 2.0.2-2 has caused the Debian Bug report #818420, regarding ices2: FTBFS: required file `./depcomp' not found to be marked as done. This means that

Bug#818288: marked as done (afl: FTBFS on s390x)

Your message dated Thu, 24 Mar 2016 23:26:34 + with message-id and subject line Bug#818288: fixed in afl 2.08b-4 has caused the Debian Bug report #818288, regarding afl: FTBFS on s390x to be marked as done. This means that you claim that the problem has

Bug#818420: marked as pending

tag 818420 pending thanks Hello, Bug #818420 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=pkg-multimedia/ices2.git;a=commitdiff;h=0e4f29c --- commit

Processed: Bug#818420 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 818420 pending Bug #818420 [ices2] ices2: FTBFS: required file `./depcomp' not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 818420:

Bug#813427: marked as done (fglrx-driver: Updating / installing libfglrx-amdxvba1 fails with a conflict)

Your message dated Thu, 24 Mar 2016 23:17:11 + with message-id and subject line Bug#813427: fixed in fglrx-driver 1:15.9-4~deb8u2 has caused the Debian Bug report #813427, regarding fglrx-driver: Updating / installing libfglrx-amdxvba1 fails with a

Bug#804445: marked as done (libsndfile: CVE-2015-7805: Heap overflow vulnerability when parsing specially crafted AIFF header)

Your message dated Thu, 24 Mar 2016 23:18:03 + with message-id and subject line Bug#804445: fixed in libsndfile 1.0.25-9.1+deb8u1 has caused the Debian Bug report #804445, regarding libsndfile: CVE-2015-7805: Heap overflow vulnerability when parsing

Bug#806376: marked as done (redmine: CVE-2015-8346: Data disclosure on the time logging form)

Your message dated Thu, 24 Mar 2016 23:18:16 + with message-id and subject line Bug#806376: fixed in redmine 3.0~20140825-8~deb8u2 has caused the Debian Bug report #806376, regarding redmine: CVE-2015-8346: Data disclosure on the time logging form to be

Bug#807272: marked as done (redmine: CVE-2015-8474: open redirect vulnerability)

Your message dated Thu, 24 Mar 2016 23:18:16 + with message-id and subject line Bug#807272: fixed in redmine 3.0~20140825-8~deb8u2 has caused the Debian Bug report #807272, regarding redmine: CVE-2015-8474: open redirect vulnerability to be marked as done.

Bug#819078: marked as done (ruby-uconv ships without a gemspec file)

Your message dated Thu, 24 Mar 2016 22:48:49 + with message-id and subject line Bug#819078: fixed in ruby-uconv 0.6.1-3 has caused the Debian Bug report #819078, regarding ruby-uconv ships without a gemspec file to be marked as done. This means that you

Bug#815802: marked as done (ruby-gir-ffi: Requiring 'gir_ffi' fails)

Your message dated Thu, 24 Mar 2016 22:48:44 + with message-id and subject line Bug#815802: fixed in ruby-gir-ffi 0.9.0-2 has caused the Debian Bug report #815802, regarding ruby-gir-ffi: Requiring 'gir_ffi' fails to be marked as done. This means that you

Bug#818288: marked as pending

tag 818288 pending thanks Hello, Bug #818288 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=collab-maint/afl.git;a=commitdiff;h=9cba00d --- commit

Processed: Bug#818288 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 818288 pending Bug #818288 [afl] afl: FTBFS on s390x Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 818288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818288 Debian Bug Tracking

Bug#819191: marked as done (apktool: unusable due to deserialization errors)

Your message dated Thu, 24 Mar 2016 22:34:59 + with message-id and subject line Bug#819191: fixed in apktool 2.0.2+dfsg-2 has caused the Debian Bug report #819191, regarding apktool: unusable due to deserialization errors to be marked as done. This means

Bug#815880: marked as done (Fails to update /etc/resolv.conf with network-manager 1.1.90)

Your message dated Thu, 24 Mar 2016 22:38:24 + with message-id and subject line Bug#815880: fixed in dnssec-trigger 0.13~svn685-5 has caused the Debian Bug report #815880, regarding Fails to update /etc/resolv.conf with network-manager 1.1.90 to be marked

Bug#816775: #816775: ruby-xapian: Please depend on librubyX.Y

* Olly Betts [160324 22:56]: > On Thu, Mar 24, 2016 at 07:52:56PM +0100, Christian Hofstaedtler wrote: > > * Christian Hofstaedtler [160324 19:08]: > > This might not be completely true; but even if the .so doesn't use > > any of libruby's symbols, it's still

Bug#816029: marked as done (Should add explicit dependency)

Your message dated Thu, 24 Mar 2016 23:13:38 +0100 with message-id <1458857618.764881.559040970.61f9f...@webmail.messagingengine.com> and subject line php5.6 is no longer part of unstable has caused the Debian Bug report #816029, regarding Should add explicit dependency to be marked as done.

Bug#816775: #816775: ruby-xapian: Please depend on librubyX.Y

On Thu, Mar 24, 2016 at 07:52:56PM +0100, Christian Hofstaedtler wrote: > * Christian Hofstaedtler [160324 19:08]: > > your package implicitly depends ob libruby2.2, by means of shipping > > an .so which uses symbols from libruby2.2. libruby2.2 is about to go > > away from

Bug#819205: Broken with current gccxml

Package: python-ctypeslib Version: 0.0.0+svn20100125-5 Severity: grave Hi, gccxml since 0.9.0+git20140716-5 (dated Aug 7th, 2015) has been replaced with a wrapper against CastXML. The wrapper is not fully compatible with gccxml, which breaks most common invocations of h2xml (e.g. it's missing

Processed: retitle 818380

Processing commands for cont...@bugs.debian.org: > retitle 818380 clang-3.7: __builtin_return_address() segfaults on s390x Bug #818380 [clang-3.7] clang-3.7: segfaults on s390x Changed Bug title to 'clang-3.7: __builtin_return_address() segfaults on s390x' from 'clang-3.7: segfaults on s390x' >

Processed: forwarded 818380

Processing commands for cont...@bugs.debian.org: > forwarded 818380 https://llvm.org/bugs/show_bug.cgi?id=27060 Bug #818380 [clang-3.7] clang-3.7: segfaults on s390x Set Bug forwarded-to-address to 'https://llvm.org/bugs/show_bug.cgi?id=27060'. > thanks Stopping processing here. Please contact

Bug#818540: pepperflashplugin-nonfree: broken by new apt

Control: tag -1 -upstream +patch On Wed, 23 Mar 2016 20:48:41 -0700, Barry Grumbine wrote: > Here's a diff to v1.8.2. I tested it by setting stdouterr to different > values and it seems to fix the problem. It also adds checks for SHA256 > hashes. Tabs got mangled in copy-paste but should be OK

Processed: Re: Bug#818540: pepperflashplugin-nonfree: broken by new apt

Processing control commands: > tag -1 -upstream +patch Bug #818540 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: broken by new apt Removed tag(s) upstream. Bug #818540 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: broken by new apt Added tag(s) patch. -- 818540:

Bug#816063: SNI

The reason https://self-signed.badssl.com works is because Emacs 24 does not do SNI; badssl.com serves up a cert valid for "*.badssl.com" in the absence of SNI, which is perfectly valid for self-signed.badssl.com. This is apparently fixed upstream already:

Bug#815742: verbiste: why verbiste is removed from testing ???

Package: verbiste Followup-For: Bug #815742 Dear Maintainer, Why did you removed verbiste from testing due to this bug which is resolved ??? BR. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing')

Bug#816775: #816775: ruby-xapian: Please depend on librubyX.Y

Hi, * Christian Hofstaedtler [160324 19:08]: > your package implicitly depends ob libruby2.2, by means of shipping > an .so which uses symbols from libruby2.2. libruby2.2 is about to go > away from testing. This might not be completely true; but even if the .so doesn't use any

Bug#819198: Missing libapache2-mod-auth-radius on Debian 8.3 mirrors.

Package: libapache2-mod-auth-radius Version: 1.5 Severity: serious Tags: upstream Justification: fails to build from source (but built successfully in the past) The package libapache2-mod-auth-radius is not on Debian mirrors. I did not find why this package was excluded from mirrors. Is there a

Bug#816313: not only for -c

Just lost a couple hours due to this bug. What Vincent reported seems debatable as -c is explicitely documented as "Read commands from the command_string operand instead of from the standard input." which suggests the file is to be interpreted as a shell script. But same happens for ./foo or

Processed: Re: #816775: ruby-xapian: Please depend on librubyX.Y

Processing control commands: > severity -1 serious Bug #816775 [ruby-xapian] Please depend on librubyX.Y Severity set to 'serious' from 'normal' > retitle -1 Missing dependency on libruby2.2, about to go away Bug #816775 [ruby-xapian] Please depend on librubyX.Y Changed Bug title to 'Missing

Bug#817818: #817818: ruby-pgplot: out of date binaries on i386

Unclear why or by whom, but i386 binaries do exist now. -- ,''`. Christian Hofstaedtler : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `-

Bug#812087: [pcscd] takes 100 % cpu

Le 15/03/2016 19:14, Ludovic Rousseau a écrit : Maybe enabling libusb debug would help. I will try to document how to do that easily. Philippe, Gustavo, Eric, can you do: $ sudo LIBUSB_DEBUG=99 pcscd -dfaT | tee log.txt generate the problem and send me the created log.txt file? Thanks --

Bug#817818: marked as done (ruby-pgplot: out of date binaries on i386)

Your message dated Thu, 24 Mar 2016 18:53:56 +0100 with message-id <20160324175356.ga15...@percival.namespace.at> and subject line Re: #817818: ruby-pgplot: out of date binaries on i386 has caused the Debian Bug report #817818, regarding ruby-pgplot: out of date binaries on i386 to be marked as

Bug#812087: [pcscd] takes 100 % cpu

Hello, For an unknown reason this email is not visible on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087 Sending it again. Le 15/03/2016 19:14, Ludovic Rousseau a écrit : On Mon, 7 Mar 2016 21:14:48 +0100 Philippe Teuwen wrote: > > > On 03/07/2016 07:34 PM,

Bug#818997: [pkg-gnupg-maint] Bug#818997: gpgv.exe linked dynamically against zlib1, doesn't allow proper signature verification

On Thu, Mar 24, 2016 at 03:07:01PM +0100, Didier 'OdyX' Raboud wrote: > Le mercredi, 23 mars 2016, 23.14:59 Daniel Kahn Gillmor a écrit : > > On Tue 2016-03-22 12:49:10 -0400, Didier 'OdyX' Raboud wrote: > > > (By the way, the CI seems to have never run successfully in the last > > > months:

Bug#819105: marked as done (openipmi: libopenimpi* basically empty)

Your message dated Thu, 24 Mar 2016 17:22:33 + with message-id and subject line Bug#819105: fixed in openipmi 2.0.21-1.2 has caused the Debian Bug report #819105, regarding openipmi: libopenimpi* basically empty to be marked as done. This means that you

Bug#819191: apktool: unusable due to deserialization errors

Package: apktool Version: 2.0.2+dfsg-1 Severity: grave Apktool is currently almost unusable because it was necessary to replace the non-free class LEDataInputStream.java with a free alternative. This alternative was not a drop-in-replacement and caused runtime errors. I intend to fix this issue

Bug#819190: libgl1-nvidia-legacy-340xx-glx: post-installation-Skript returns error code 137

Package: libgl1-nvidia-legacy-340xx-glx Version: 340.96-3 Severity: critical Justification: breaks the whole system First I deinstalled all of nvidia apt-get --purge remove *nvidia* apt-get install nvidia-detect Check for needed legacy-driver apt-get install nvidia-legacy-340xx-driver

Bug#819187: ruby-compass: FTBFS: Invalid gemspec in [compass-import-once.gemspec]: No such file or directory @ rb_sysopen

Source: ruby-compass Version: 1.0.3~dfsg-3 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ruby-compass fails to build from source in

Bug#819105: openipmi: libopenimpi* basically empty

Re: Aaron M. Ucko 2016-03-23 <145876268308.18250.15488299010633533232.report...@ghostwheel.internal.ucko.debian.net> > Source: openipmi > Version: 2.0.21-1.1 > Severity: grave > Justification: renders package unusable > > As of version 2.0.21-1.1, libopenipmi0 and libopenipmi-dev don't > contain

Bug#818308: marked as done (openjdk-7-jre-headless: openjdk-7 uninstallable because tzdata-java removed)

Your message dated Thu, 24 Mar 2016 16:05:22 + with message-id and subject line Bug#818308: fixed in openjdk-7 7u95-2.6.4-3 has caused the Debian Bug report #818308, regarding openjdk-7-jre-headless: openjdk-7 uninstallable because tzdata-java removed to

Bug#819042: nvidia-graphics-drivers: Package uninstallable using unstable

On 23 March 2016 at 07:59, Eric Valette wrote: > Source: nvidia-graphics-drivers > Version: 355.11-3 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Unstable provides for months an video abi 20 and the upstream package provide > no support

Bug#819042: nvidia-graphics-drivers: Package uninstallable using unstable

On 03/24/2016 03:51 PM, Luca Boccassi wrote: On 23 March 2016 at 07:59, Eric Valette wrote: Hi Eric, Hi, We have an upload with new binaries stuck in the NEW queue for a month now: https://ftp-master.debian.org/new/nvidia-graphics-drivers_355.11-3.html Until this

Bug#819179: quagga: CVE-2016-2342

Source: quagga Version: 0.99.22.4-1 Severity: grave Tags: security upstream patch fixed-upstream Hi, the following vulnerability was published for quagga. CVE-2016-2342[0]: | The bgp_nlri_parse_vpnv4 function in bgp_mplsvpn.c in the VPNv4 NLRI | parser in bgpd in Quagga before 1.0.20160309,

Bug#818997: [pkg-gnupg-maint] Bug#818997: gpgv.exe linked dynamically against zlib1, doesn't allow proper signature verification

Le mercredi, 23 mars 2016, 23.14:59 Daniel Kahn Gillmor a écrit : > On Tue 2016-03-22 12:49:10 -0400, Didier 'OdyX' Raboud wrote: > > I've noticed that gpgv.exe fails its CI test > > (debian/tests/gpgv-win32) in version 1.4.20-4 (-3 and previous work > > fine): > > interesting, there was no

Bug#819174: Fails to start with missing cache dir

Package: mopidy Version: 2.0.0-1 Severity: serious If /var/cache/mopidy is lost (e.g. because /var/cache is a tmpfs), mopidy fails to start. However, the FHS specifies that files in /var/cache must not be relied upon. The problem here is that mopidy tries to create the directory but fails due to

Bug#819162: marked as done (pacemaker: Missing dependency on dbus)

Your message dated Thu, 24 Mar 2016 13:50:10 + with message-id and subject line Bug#819162: fixed in pacemaker 1.1.14-3 has caused the Debian Bug report #819162, regarding pacemaker: Missing dependency on dbus to be marked as done. This means that you

Bug#764484: dwarves-dfsg: FTBFS with newer elfutils

Control: tags -1 pending Hi, I have prepared an NMU to fix this bug and uploaded it to DELAYED/2. Please tell me if you want me to cancel it. The NMU debdiff is attached. Thanks, Jamesdiff -Nru dwarves-dfsg-1.10/debian/changelog dwarves-dfsg-1.10/debian/changelog ---

Processed: Bug#764484: dwarves-dfsg: FTBFS with newer elfutils

Processing control commands: > tags -1 pending Bug #764484 [dwarves-dfsg] dwarves-dfsg: FTBFS with newer elfutils Added tag(s) pending. -- 764484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#811190: util-vserver: diff for NMU version 0.30.216-pre3120-1.1

Control: tags -1 patch pending Hi, I have prepared a NMU to fix #811190 (RC bug which prevents the package building) and #604988 (allows beecrypt to be removed from the archive) and uploaded it to DELAYED/2. Please tell me if you want me to cancel it. The NMU debdiff is attached. Thanks,

Processed: util-vserver: diff for NMU version 0.30.216-pre3120-1.1

Processing control commands: > tags -1 patch pending Bug #811190 [src:util-vserver] util-vserver: please switch B-D from module-init-tools to kmod Added tag(s) patch and pending. -- 811190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811190 Debian Bug Tracking System Contact

Bug#817789: Fixed the bug

On Fri, Mar 18, 2016 at 18:54:50 +0100, Georges Khaznadar wrote: > Hi, > It was just adding a new dependency. > > I need blogdiag as a dependency of seelablet, so I have made a NMU to > delayed+9. > You're supposed to send NMU diffs to the BTS... Cheers, Julien -- Julien Cristau

Bug#818411: marked as done (urlview: FTBFS: required file `./missing' not found)

Your message dated Thu, 24 Mar 2016 12:34:44 + with message-id and subject line Bug#818411: fixed in urlview 0.9-20 has caused the Debian Bug report #818411, regarding urlview: FTBFS: required file `./missing' not found to be marked as done. This means

Processed: Re: signon-ui: runaway dbus-daemon during build

Processing commands for cont...@bugs.debian.org: > severity 805389 serious Bug #805389 [src:signon-ui] signon-ui: runaway dbus-daemon during build Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 805389:

Bug#818187: zeromq3 migrated without any transition being done

On Thu, 24 Mar 2016 11:59:44 0100 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote: > On Thu, Mar 24, 2016 at 11:54 AM, Emilio Pozuelo Monfort > wrote: > > On 21/03/16 19:59, Luca Boccassi wrote: > >> Given the change of the -dev package name here,

Bug#819162: pacemaker: Missing dependency on dbus

Package: pacemaker Version: 1.1.14-2 Severity: serious Hello, pacemaker is missing a dependency on "dbus", without it installation and start will fail: resource-agents (1:3.9.7-1~bpo8+1) wird eingerichtet ... pacemaker-resource-agents (1.1.14-2~bpo8+1) wird eingerichtet ... pacemaker

Bug#818187: zeromq3 migrated without any transition being done

On Thu, Mar 24, 2016 at 11:54 AM, Emilio Pozuelo Monfort wrote: > On 21/03/16 19:59, Luca Boccassi wrote: >> Given the change of the -dev package name here, should I roll back and b-d >> again on libzmq3-dev? I don't mind doing another upload if it's the right >> thing. > >

Processed: tagging 818156

Processing commands for cont...@bugs.debian.org: > tags 818156 + fixed-upstream Bug #818156 {Done: Jean-Michel Vourgère } [src:rrdtool] rrdtool: FTBFS: ./functions: line 72: : command not found Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me

Bug#818187: zeromq3 migrated without any transition being done

On 21/03/16 19:59, Luca Boccassi wrote: > Given the change of the -dev package name here, should I roll back and b-d > again on libzmq3-dev? I don't mind doing another upload if it's the right > thing. Yes that'd be fine, but there's no rush. Cheers, Emilio

Bug#818926: perl6-panda: panda doesn't start up / find needed libraries

On Wed, 23 Mar 2016 17:01:14 +0100 Dominique Dumont wrote: > From what I've understood, distro packaging is not a feature of Panda. Some > other tool must be developed by upstream. I'll follow what's going on there. First stab at install tool is:

Bug#819113: marked as done (openarena: unpure pak6-patch088.pk3 is downloaded from server)

Your message dated Thu, 24 Mar 2016 10:24:46 + with message-id and subject line Bug#819113: fixed in openarena-088-data 0.8.8-5 has caused the Debian Bug report #819113, regarding openarena: unpure pak6-patch088.pk3 is downloaded from server to be marked

Processed: Re: Bug#799724: Bug is still present in caldav version of the package

Processing control commands: > block -1 by 802331 Bug #799724 {Done: Ondřej Surý } [cyrus-replication] cyrus-replication broken / wrong connection 799724 was not blocked by any bugs. 799724 was not blocking any bugs. Added blocking bug(s) of 799724: 802331 -- 799724:

Bug#799724: Bug is still present in caldav version of the package

Control: block -1 by 802331 Update in jessie is in progress. But the change is quite intrusive and hence not taken lightly. Cheers, -- Ondřej Surý Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server On Fri, Jan 29, 2016, at 17:06, Deyan Stanev wrote: > Hello,

Processed: Re: Bug#819113: openarena: unpure pak6-patch088.pk3 is downloaded from server

Processing control commands: > reassign 819113 openarena-088-data Bug #819113 [openarena] openarena: unpure pak6-patch088.pk3 is downloaded from server Bug reassigned from package 'openarena' to 'openarena-088-data'. No longer marked as found in versions openarena/0.8.8-15. Ignoring request to

Processed: Re: Please leave the severity at serious, this bug is a security issue.

Processing control commands: > affects -1 suricata Bug #819050 [libpcre3] libpcre3 segfaults on certain regex when jit is used Added indication that 819050 affects suricata -- 819050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819050 Debian Bug Tracking System Contact

Bug#819050: Please leave the severity at serious, this bug is a security issue.

control: affects -1 suricata On jeu., 2016-03-24 at 07:20 +0100, Florian Weimer wrote: > * Hilko Bengen: > > > > > the original report may not have been 100% clear on this, but the bug is > > the main cause of a vulnerability in Suricata (a network IDS/IPS) that > > allows for remote denial of

Bug#819050: Please leave the severity at serious, this bug is a security issue.

* Hilko Bengen: > the original report may not have been 100% clear on this, but the bug is > the main cause of a vulnerability in Suricata (a network IDS/IPS) that > allows for remote denial of service, possibly remote code execution by > simply passing crafted packets by a Suricata installation.

Bug#817929: marked as done (mosh fails to connect, giving a UDP error)

Your message dated Thu, 24 Mar 2016 06:19:21 + with message-id and subject line Bug#817929: fixed in mosh 1.2.5-2 has caused the Debian Bug report #817929, regarding mosh fails to connect, giving a UDP error to be marked as done. This means that you claim