Bug#681510: marked as done (debhelper: dh_install --fail-missing defaults to . as sourcedir even when install itself uses debian/tmp)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 06:53:00 + with message-id <06c75be6-64ee-a0d2-b6c7-d42e2ad5b...@thykier.net> and subject line Re: debhelper: dh_install --fail-missing defaults to . as sourcedir even when install itself uses debian/tmp has caused the Debian Bug report #681510, regarding de

Bug#827076: marked as done (src:gridengine: FTBFS with openssl 1.1.0)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 05:49:41 + with message-id and subject line Bug#827076: fixed in gridengine 8.1.9+dfsg-6 has caused the Debian Bug report #827076, regarding src:gridengine: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been d

Bug#828329: marked as done (gridengine: FTBFS with openssl 1.1.0)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 05:49:41 + with message-id and subject line Bug#827076: fixed in gridengine 8.1.9+dfsg-6 has caused the Debian Bug report #827076, regarding gridengine: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#875972: marked as done (cloudprint-service: cloudprintd.service should start after network-online.target)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 05:18:53 + with message-id and subject line Bug#875972: fixed in cloudprint 0.14-9 has caused the Debian Bug report #875972, regarding cloudprint-service: cloudprintd.service should start after network-online.target to be marked as done. This means that yo

Bug#882104: marked as done (debian-goodies: "checkrestart -n" throws TypeError: a bytes-like object is required, not 'str')

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:48:45 + with message-id and subject line Bug#882104: fixed in debian-goodies 0.78 has caused the Debian Bug report #882104, regarding debian-goodies: "checkrestart -n" throws TypeError: a bytes-like object is required, not 'str' to be marked as done. Th

Bug#882080: marked as done (debian-goodies: checkrestart from debian-goodies 0.77 finds no files to restart)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:48:45 + with message-id and subject line Bug#882080: fixed in debian-goodies 0.78 has caused the Debian Bug report #882080, regarding debian-goodies: checkrestart from debian-goodies 0.77 finds no files to restart to be marked as done. This means that y

Bug#877621: marked as done (RM: maxima [hurd-i386] -- RoQA; B-D unavailable)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:04:24 + with message-id and subject line Bug#877621: Removed package(s) from unstable has caused the Debian Bug report #877621, regarding RM: maxima [hurd-i386] -- RoQA; B-D unavailable to be marked as done. This means that you claim that the problem has

Bug#877615: marked as done (RM: bangarang -- ROM; depends on Qt4 and abandoned upstream)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:02:40 + with message-id and subject line Bug#877615: Removed package(s) from unstable has caused the Debian Bug report #877615, regarding RM: bangarang -- ROM; depends on Qt4 and abandoned upstream to be marked as done. This means that you claim that the

Bug#722183: marked as done (Package bangarang outdated)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:02:45 + with message-id and subject line Bug#877615: Removed package(s) from unstable has caused the Debian Bug report #722183, regarding Package bangarang outdated to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#874828: marked as done ([bangarang] Future Qt4 removal from Buster)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:02:45 + with message-id and subject line Bug#877615: Removed package(s) from unstable has caused the Debian Bug report #874828, regarding [bangarang] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#877531: marked as done (RM: mongodb [hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- ANAIS; restricted to fewer architectures)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:47 + with message-id and subject line Bug#877531: Removed package(s) from unstable has caused the Debian Bug report #877531, regarding RM: mongodb [hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- ANAIS; restricted to fewer architectures to be marked as don

Bug#853086: marked as done (livestreamer: Can't play twitch streams: Client Error: Bad Request for url)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:23 + with message-id and subject line Bug#877485: Removed package(s) from unstable has caused the Debian Bug report #853086, regarding livestreamer: Can't play twitch streams: Client Error: Bad Request for url to be marked as done. This means that yo

Bug#877611: marked as done (RM: tor [hurd-i386] -- ROM; obsolete binary)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:02:06 + with message-id and subject line Bug#877611: Removed package(s) from unstable has caused the Debian Bug report #877611, regarding RM: tor [hurd-i386] -- ROM; obsolete binary to be marked as done. This means that you claim that the problem has bee

Bug#839384: marked as done (livestreamer: include several fixes before Stretch freeze)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:23 + with message-id and subject line Bug#877485: Removed package(s) from unstable has caused the Debian Bug report #839384, regarding livestreamer: include several fixes before Stretch freeze to be marked as done. This means that you claim that the p

Bug#877465: marked as done (RM: massxpert -- RoQA; superseded by msxpertsuite)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:00:52 + with message-id and subject line Bug#877465: Removed package(s) from unstable has caused the Debian Bug report #877465, regarding RM: massxpert -- RoQA; superseded by msxpertsuite to be marked as done. This means that you claim that the problem h

Bug#877485: marked as done (RM: livestreamer -- ROM; dead upstream. Has still maintained fork under new name (streamlink))

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:16 + with message-id and subject line Bug#877485: Removed package(s) from unstable has caused the Debian Bug report #877485, regarding RM: livestreamer -- ROM; dead upstream. Has still maintained fork under new name (streamlink) to be marked as done.

Bug#877407: marked as done (RM: nodejs-legacy -- RoQA; needs manual decruft)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:00:31 + with message-id and subject line Bug#877407: Removed package(s) from unstable has caused the Debian Bug report #877407, regarding RM: nodejs-legacy -- RoQA; needs manual decruft to be marked as done. This means that you claim that the problem has

Bug#805784: marked as done (python-livestreamer: Twitch support is broken in Jessie)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:23 + with message-id and subject line Bug#877485: Removed package(s) from unstable has caused the Debian Bug report #805784, regarding python-livestreamer: Twitch support is broken in Jessie to be marked as done. This means that you claim that the pro

Bug#762234: marked as done (livestreamer: English Club)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 01:01:23 + with message-id and subject line Bug#877485: Removed package(s) from unstable has caused the Debian Bug report #762234, regarding livestreamer: English Club to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#877197: marked as done (readline6 FTBFS with debhelper 10.9)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #877197, regarding readline6 FTBFS with debhelper 10.9 to be marked as done. This means that you claim that the problem has been dealt

Bug#877406: marked as done (RM: nanopolish [armhf mips powerpc s390x] -- NBS; no longer built on non-x86)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:59:25 + with message-id and subject line Bug#877406: Removed package(s) from unstable has caused the Debian Bug report #877406, regarding RM: nanopolish [armhf mips powerpc s390x] -- NBS; no longer built on non-x86 to be marked as done. This means that

Bug#857297: marked as done (lib32readline6:s390x is an empty package)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #857297, regarding lib32readline6:s390x is an empty package to be marked as done. This means that you claim that the problem has been d

Bug#877240: marked as done (RM: readline6 -- ROM; obsolete version of readline)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:57:58 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #877240, regarding RM: readline6 -- ROM; obsolete version of readline to be marked as done. This means that you claim that the problem

Bug#877332: marked as done (RM: p3scan -- RoQA; orphaned, dead upstream)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:46 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #877332, regarding RM: p3scan -- RoQA; orphaned, dead upstream to be marked as done. This means that you claim that the problem has bee

Bug#877399: marked as done (RM: algobox [armel kfreebsd-amd64 kfreebsd-i386 mips mips64el powerpc ppc64el s390x] -- ANAIS; Build-depend on qtwebengine5-dev not available anymore in some architectures)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:59:12 + with message-id and subject line Bug#877399: Removed package(s) from unstable has caused the Debian Bug report #877399, regarding RM: algobox [armel kfreebsd-amd64 kfreebsd-i386 mips mips64el powerpc ppc64el s390x] -- ANAIS; Build-depend on qtweb

Bug#876674: marked as done (p3scan: CVE-2017-14681)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #876674, regarding p3scan: CVE-2017-14681 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#877327: marked as done (RM: s3backer [kfreebsd-amd64 kfreebsd-i386] -- RoQA; B-D fuse only available on linux)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:25 + with message-id and subject line Bug#877327: Removed package(s) from unstable has caused the Debian Bug report #877327, regarding RM: s3backer [kfreebsd-amd64 kfreebsd-i386] -- RoQA; B-D fuse only available on linux to be marked as done. This me

Bug#848170: marked as done (readline: Please drop the multilib packages)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #848170, regarding readline: Please drop the multilib packages to be marked as done. This means that you claim that the problem has bee

Bug#840397: marked as done (stretch should not ship with readline6)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #840397, regarding stretch should not ship with readline6 to be marked as done. This means that you claim that the problem has been dea

Bug#363502: marked as done (libreadline6: Something is wrong with binding keys to functions)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #363502, regarding libreadline6: Something is wrong with binding keys to functions to be marked as done. This means that you claim that

Bug#750874: marked as done (p3scan: FTBFS with clang instead of gcc)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #750874, regarding p3scan: FTBFS with clang instead of gcc to be marked as done. This means that you claim that the problem has been de

Bug#241232: marked as done (p3scan: Allow running just spamassassin)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #241232, regarding p3scan: Allow running just spamassassin to be marked as done. This means that you claim that the problem has been de

Bug#701931: marked as done (readline6: Consider a non-free documentation package)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #701931, regarding readline6: Consider a non-free documentation package to be marked as done. This means that you claim that the proble

Bug#577012: marked as done (libreadline6 clobbers xterm's eightBitInput ressource and doesn't restore it)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #577012, regarding libreadline6 clobbers xterm's eightBitInput ressource and doesn't restore it to be marked as done. This means that

Bug#778433: marked as done (p3scan: please make the build reproducible)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #778433, regarding p3scan: please make the build reproducible to be marked as done. This means that you claim that the problem has been

Bug#475833: marked as done (p3scan 'emailport' option does not start daemon listening on specified port)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #475833, regarding p3scan 'emailport' option does not start daemon listening on specified port to be marked as done. This means that y

Bug#574518: marked as done (please set enable-meta-key (_rl_enable_meta) sanely)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #574518, regarding please set enable-meta-key (_rl_enable_meta) sanely to be marked as done. This means that you claim that the problem

Bug#591632: marked as done (multi-byte characters in history: incremental search bug)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #591632, regarding multi-byte characters in history: incremental search bug to be marked as done. This means that you claim that the pr

Bug#309582: marked as done (p3scan: hangs while getting new ip)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #309582, regarding p3scan: hangs while getting new ip to be marked as done. This means that you claim that the problem has been dealt w

Bug#608517: marked as done (libreadline6: Command mode vs insert mode indicator with vi key bindings)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #608517, regarding libreadline6: Command mode vs insert mode indicator with vi key bindings to be marked as done. This means that you

Bug#761459: marked as done (libreadline6: terminfo delays not honored, visible bell nearly invisible)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #761459, regarding libreadline6: terminfo delays not honored, visible bell nearly invisible to be marked as done. This means that you

Bug#737955: marked as done (readline6: Patch to bootstrap without multilib or texinfo)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #737955, regarding readline6: Patch to bootstrap without multilib or texinfo to be marked as done. This means that you claim that the p

Bug#771487: marked as done (O: p3scan -- transparent POP3-proxy with virus- and spam-scanning)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #771487, regarding O: p3scan -- transparent POP3-proxy with virus- and spam-scanning to be marked as done. This means that you claim th

Bug#783136: marked as done (readline6: plese make the build reproducible)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #783136, regarding readline6: plese make the build reproducible to be marked as done. This means that you claim that the problem has be

Bug#773891: marked as done (libreadline6: inputrc with some comments causes libreadline6 linked program(s) to segfault)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #773891, regarding libreadline6: inputrc with some comments causes libreadline6 linked program(s) to segfault to be marked as done. Th

Bug#339004: marked as done (p3scan: child died with abnormal termsignal (11))

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #339004, regarding p3scan: child died with abnormal termsignal (11) to be marked as done. This means that you claim that the problem ha

Bug#556583: marked as done (libreadline6: break reportbug Ctrl+c)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:12 + with message-id and subject line Bug#877240: Removed package(s) from unstable has caused the Debian Bug report #556583, regarding libreadline6: break reportbug Ctrl+c to be marked as done. This means that you claim that the problem has been dealt

Bug#241234: marked as done (p3scan: Provide way to tune spamassassin bayesian statistics)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:58:56 + with message-id and subject line Bug#877332: Removed package(s) from unstable has caused the Debian Bug report #241234, regarding p3scan: Provide way to tune spamassassin bayesian statistics to be marked as done. This means that you claim that th

Bug#876769: marked as done (RM: libidn2-0-dev [all] -- RoQA; obsolete arch:all package)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:24:05 + with message-id and subject line Bug#876769: Removed package(s) from unstable has caused the Debian Bug report #876769, regarding RM: libidn2-0-dev [all] -- RoQA; obsolete arch:all package to be marked as done. This means that you claim that the

Bug#871156: marked as done (pyfits: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:22:34 + with message-id and subject line Bug#869858: Removed package(s) from unstable has caused the Debian Bug report #871156, regarding pyfits: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security] to be marked as done

Bug#872195: marked as done (tircd: fails to install: chown: cannot access '/var/lib/tircd': No such file or directory)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:20:30 + with message-id and subject line Bug#872195: fixed in tircd 0.30-4 has caused the Debian Bug report #872195, regarding tircd: fails to install: chown: cannot access '/var/lib/tircd': No such file or directory to be marked as done. This means tha

Bug#844087: marked as done (Please consider removing pyfits)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:22:34 + with message-id and subject line Bug#869858: Removed package(s) from unstable has caused the Debian Bug report #844087, regarding Please consider removing pyfits to be marked as done. This means that you claim that the problem has been dealt with

Bug#869858: marked as done (RM: pyfits -- ROM; superseeded by astropy)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:22:29 + with message-id and subject line Bug#869858: Removed package(s) from unstable has caused the Debian Bug report #869858, regarding RM: pyfits -- ROM; superseeded by astropy to be marked as done. This means that you claim that the problem has been

Bug#875131: marked as done (RM: qimhangul -- ROM; unmaintained, QT4 dependent)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:23:17 + with message-id and subject line Bug#875131: Removed package(s) from unstable has caused the Debian Bug report #875131, regarding RM: qimhangul -- ROM; unmaintained, QT4 dependent to be marked as done. This means that you claim that the problem h

Bug#881964: marked as done (hatariui fails to start)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 23:49:30 + with message-id and subject line Bug#881964: fixed in hatari 2.0.0+dfsg-4 has caused the Debian Bug report #881964, regarding hatariui fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#881961: marked as done (hatari: lacks dependency to python-gtk2)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 23:49:30 + with message-id and subject line Bug#881961: fixed in hatari 2.0.0+dfsg-4 has caused the Debian Bug report #881961, regarding hatari: lacks dependency to python-gtk2 to be marked as done. This means that you claim that the problem has been dealt

Bug#872716: marked as done (mark itstool Multi-Arch: foreign)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 23:33:45 + with message-id and subject line Bug#872716: fixed in itstool 2.0.2-3.1 has caused the Debian Bug report #872716, regarding mark itstool Multi-Arch: foreign to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#882073: marked as done (firefox: Disable Pocket by default: a non-free web service and privacy relevant that should require consent)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 07:39:47 +0900 with message-id <20171118223947.5ymxcasjdv4fk...@glandium.org> and subject line Re: Bug#882073: firefox: Disable Pocket by default: a non-free web service and privacy relevant that should require consent has caused the Debian Bug report #882073, r

Bug#882067: marked as done (footnote for kernel-parameters.txt references a broken link)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sun, 19 Nov 2017 00:01:27 +0100 with message-id and subject line Re: Bug#882067: footnote for kernel-parameters.txt references a broken link has caused the Debian Bug report #882067, regarding footnote for kernel-parameters.txt references a broken link to be marked as done. T

Bug#578337: marked as done (libgc: Fixing FTBFS (7.1))

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 23:57:07 +0100 with message-id <20171118225704.oolghqp7k2xpk...@reva.itsari.org> and subject line Re: Bug#578337: libgc: Fixing FTBFS (7.1) has caused the Debian Bug report #578337, regarding libgc: Fixing FTBFS (7.1) to be marked as done. This means that you cl

Processed: unarchiving 876001, closing 876001, archiving 876001

2017-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 876001 Bug #876001 {Done: Rene Engelhard } [src:libwpd] libwpd: CVE-2017-14226 Unarchived Bug 876001 > close 876001 0.10.0-2+deb8u1 Bug #876001 {Done: Rene Engelhard } [src:libwpd] libwpd: CVE-2017-14226 Marked as fixed in versions lib

Bug#879055: marked as done (mupdf: CVE-2017-15587)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:20:55 + with message-id and subject line Bug#879055: fixed in mupdf 1.5-1+deb8u3 has caused the Debian Bug report #879055, regarding mupdf: CVE-2017-15587 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#876462: marked as done (otrs2: CVE-2017-14635: Code Injection / Privilege Escalation OTRS)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:21:22 + with message-id and subject line Bug#876462: fixed in otrs2 3.3.18-1+deb8u1 has caused the Debian Bug report #876462, regarding otrs2: CVE-2017-14635: Code Injection / Privilege Escalation OTRS to be marked as done. This means that you claim that

Bug#878402: marked as done (Security fixes from the October 2017 CPU)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:21:00 + with message-id and subject line Bug#878402: fixed in mysql-5.5 5.5.58-0+deb8u1 has caused the Debian Bug report #878402, regarding Security fixes from the October 2017 CPU to be marked as done. This means that you claim that the problem has been

Bug#879474: marked as done (quagga-bgpd: CVE-2017-16227: BGP session termination due to rather long AS paths in update messages)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:21:36 + with message-id and subject line Bug#879474: fixed in quagga 0.99.23.1-1+deb8u4 has caused the Debian Bug report #879474, regarding quagga-bgpd: CVE-2017-16227: BGP session termination due to rather long AS paths in update messages to be marked a

Bug#879521: marked as done (irssi: multiple vulnerabilities fixed in irssi 1.0.5)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:55 + with message-id and subject line Bug#879521: fixed in irssi 0.8.17-1+deb8u5 has caused the Debian Bug report #879521, regarding irssi: multiple vulnerabilities fixed in irssi 1.0.5 to be marked as done. This means that you claim that the problem

Bug#881586: marked as done (Konversation CVE-2017-15923)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:19:01 + with message-id and subject line Bug#881586: fixed in konversation 1.5-2+deb8u1 has caused the Debian Bug report #881586, regarding Konversation CVE-2017-15923 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#878578: marked as done (imagemagick: CVE-2017-15277)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:46 + with message-id and subject line Bug#878578: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #878578, regarding imagemagick: CVE-2017-15277 to be marked as done. This means that you claim that the problem has been dealt

Bug#880116: marked as done (CVE-2017-15953 / CVE-2017-15954 / CVE-2017-15955)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:17:26 + with message-id and subject line Bug#880116: fixed in bchunk 1.2.0-12+deb8u1 has caused the Debian Bug report #880116, regarding CVE-2017-15953 / CVE-2017-15954 / CVE-2017-15955 to be marked as done. This means that you claim that the problem has

Bug#879001: marked as done (CVE-2017-12197: libpam4j: Account check bypass)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:19:23 + with message-id and subject line Bug#879001: fixed in libpam4j 1.4-2+deb8u1 has caused the Debian Bug report #879001, regarding CVE-2017-12197: libpam4j: Account check bypass to be marked as done. This means that you claim that the problem has be

Bug#881392: marked as done (imagemagick: CVE-2017-16546)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:46 + with message-id and subject line Bug#881392: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #881392, regarding imagemagick: CVE-2017-16546 to be marked as done. This means that you claim that the problem has been dealt

Bug#876097: marked as done (imagemagick: CVE-2017-14224: Heap buffer overflow in WritePCXImage)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#876097: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #876097, regarding imagemagick: CVE-2017-14224: Heap buffer overflow in WritePCXImage to be marked as done. This means that you

Bug#878527: marked as done (imagemagick: CVE-2017-14607)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#878527: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #878527, regarding imagemagick: CVE-2017-14607 to be marked as done. This means that you claim that the problem has been dealt

Bug#878507: marked as done (imagemagick: CVE-2017-13769)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#878507: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #878507, regarding imagemagick: CVE-2017-13769 to be marked as done. This means that you claim that the problem has been dealt

Bug#873134: marked as done (imagemagick: CVE-2017-12983)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#873134: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #873134, regarding imagemagick: CVE-2017-12983 to be marked as done. This means that you claim that the problem has been dealt

Bug#878562: marked as done (imagemagick: CVE-2017-14989)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#878562: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #878562, regarding imagemagick: CVE-2017-14989 to be marked as done. This means that you claim that the problem has been dealt

Bug#872373: marked as done (CVE-2017-12877)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#872373: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #872373, regarding CVE-2017-12877 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#878508: marked as done (imagemagick: CVE-2017-13758)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#878508: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #878508, regarding imagemagick: CVE-2017-13758 to be marked as done. This means that you claim that the problem has been dealt

Bug#873099: marked as done (imagemagick: CVE-2017-13134)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#873099: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #873099, regarding imagemagick: CVE-2017-13134 to be marked as done. This means that you claim that the problem has been dealt

Bug#876488: marked as done (imagemagick: CVE-2017-14682: Heap buffer overflow in GetNextToken())

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#876488: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #876488, regarding imagemagick: CVE-2017-14682: Heap buffer overflow in GetNextToken() to be marked as done. This means that yo

Bug#870848: marked as done (jackson-databind: CVE-2017-7525: Deserialization vulnerability via readValue method of ObjectMapper)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:19:00 + with message-id and subject line Bug#870848: fixed in jackson-databind 2.4.2-2+deb8u1 has caused the Debian Bug report #870848, regarding jackson-databind: CVE-2017-7525: Deserialization vulnerability via readValue method of ObjectMapper to be ma

Bug#868469: marked as done (imagemagick: CVE-2017-11352 (Incomplete fix for CVE-2017-9144))

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#868469: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #868469, regarding imagemagick: CVE-2017-11352 (Incomplete fix for CVE-2017-9144) to be marked as done. This means that you cla

Bug#869728: marked as done (imagemagick: CVE-2017-13144)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:18:45 + with message-id and subject line Bug#869728: fixed in imagemagick 8:6.8.9.9-5+deb8u11 has caused the Debian Bug report #869728, regarding imagemagick: CVE-2017-13144 to be marked as done. This means that you claim that the problem has been dealt

Processed: unarchiving 876001, closing 876019, archiving 876001

2017-11-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 876001 Bug #876001 {Done: Rene Engelhard } [src:libwpd] libwpd: CVE-2017-14226 Unarchived Bug 876001 > close 876019 0.10.0-2+deb8u1 Bug #876019 [release.debian.org] jessie-pu: package libwpd/0.10.0-2+deb8u1 There is no source info for t

Bug#646031: marked as done (unar: creates $HOME/GNUstep/Library directory)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 22:44:35 +0100 with message-id <20171118214435.degha5pn5r2w4...@jwilk.net> and subject line Re: Bug#646031: theunarchiver: creates $HOME/GNUstep/Library directory has caused the Debian Bug report #646031, regarding unar: creates $HOME/GNUstep/Library directory t

Bug#879004: marked as done (isolinux: isohdpfx.bin fails to boot on old BIOS due to wrong stack order for heads/sectors)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:13 + with message-id and subject line Bug#879004: fixed in syslinux 3:6.03+dfsg-14.1+deb9u1 has caused the Debian Bug report #879004, regarding isolinux: isohdpfx.bin fails to boot on old BIOS due to wrong stack order for heads/sectors to be marked as

Bug#865770: marked as done (openssh-server fails to validate configuration before reloading, under systemd)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:08 + with message-id and subject line Bug#865770: fixed in openssh 1:7.4p1-10+deb9u2 has caused the Debian Bug report #865770, regarding openssh-server fails to validate configuration before reloading, under systemd to be marked as done. This means t

Bug#865462: marked as done (extlinux: fails to boot from Btrfs filesystem)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:13 + with message-id and subject line Bug#865462: fixed in syslinux 3:6.03+dfsg-14.1+deb9u1 has caused the Debian Bug report #865462, regarding extlinux: fails to boot from Btrfs filesystem to be marked as done. This means that you claim that the prob

Bug#869222: marked as done ([pdns-server] Invalid DNSSEC signatures for empty responses with DNS 0x20)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:09 + with message-id and subject line Bug#869222: fixed in pdns 4.0.3-1+deb9u1 has caused the Debian Bug report #869222, regarding [pdns-server] Invalid DNSSEC signatures for empty responses with DNS 0x20 to be marked as done. This means that you cla

Bug#833057: marked as done (extlinux: cannot boot from ext4 filesystems with 64bit feature enabled)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:13 + with message-id and subject line Bug#833057: fixed in syslinux 3:6.03+dfsg-14.1+deb9u1 has caused the Debian Bug report #833057, regarding extlinux: cannot boot from ext4 filesystems with 64bit feature enabled to be marked as done. This means tha

Bug#864818: marked as done (python-tablib: CVE-2017-2810)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:32:11 + with message-id and subject line Bug#864818: fixed in python-tablib 0.9.11-2+deb9u1 has caused the Debian Bug report #864818, regarding python-tablib: CVE-2017-2810 to be marked as done. This means that you claim that the problem has been dealt w

Bug#847258: marked as done (Updating the python-cups Uploaders list)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:10:56 + with message-id and subject line Bug#847258: fixed in python-cups 1.9.73-2 has caused the Debian Bug report #847258, regarding Updating the python-cups Uploaders list to be marked as done. This means that you claim that the problem has been dealt

Bug#878818: marked as done (ovito: FTBFS - Testsuite fails because executed with python3.5 instead of 3.6)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:10:37 + with message-id and subject line Bug#878818: fixed in ovito 2.9.0+dfsg1-3 has caused the Debian Bug report #878818, regarding ovito: FTBFS - Testsuite fails because executed with python3.5 instead of 3.6 to be marked as done. This means that you

Bug#859226: marked as done (m2ext: Please migrate to openssl1.1 in buster)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:10:25 + with message-id and subject line Bug#859226: fixed in m2ext 0.1-1.2 has caused the Debian Bug report #859226, regarding m2ext: Please migrate to openssl1.1 in buster to be marked as done. This means that you claim that the problem has been dealt

Bug#879952: marked as done (qt3d5-dev-tools: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/qt5/bin/qgltf)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:11:12 + with message-id and subject line Bug#879952: fixed in qt3d-opensource-src 5.9.2+dfsg-3 has caused the Debian Bug report #879952, regarding qt3d5-dev-tools: fails to upgrade from 'stable' to 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/qt

Bug#881586: marked as done (Konversation CVE-2017-15923)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:04:15 + with message-id and subject line Bug#881586: fixed in konversation 1.6.2-2+deb9u1 has caused the Debian Bug report #881586, regarding Konversation CVE-2017-15923 to be marked as done. This means that you claim that the problem has been dealt with

Bug#877712: marked as done (python-gunicorn: stable version brings in dpkg-dev unnecessarily)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:03:42 + with message-id and subject line Bug#877712: fixed in gunicorn 19.6.0-10+deb9u1 has caused the Debian Bug report #877712, regarding python-gunicorn: stable version brings in dpkg-dev unnecessarily to be marked as done. This means that you claim t

Bug#878578: marked as done (imagemagick: CVE-2017-15277)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:03:47 + with message-id and subject line Bug#878578: fixed in imagemagick 8:6.9.7.4+dfsg-11+deb9u3 has caused the Debian Bug report #878578, regarding imagemagick: CVE-2017-15277 to be marked as done. This means that you claim that the problem has been d

Bug#878507: marked as done (imagemagick: CVE-2017-13769)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:03:47 + with message-id and subject line Bug#878507: fixed in imagemagick 8:6.9.7.4+dfsg-11+deb9u3 has caused the Debian Bug report #878507, regarding imagemagick: CVE-2017-13769 to be marked as done. This means that you claim that the problem has been d

Bug#878508: marked as done (imagemagick: CVE-2017-13758)

2017-11-18 Thread Debian Bug Tracking System
Your message dated Sat, 18 Nov 2017 21:03:47 + with message-id and subject line Bug#878508: fixed in imagemagick 8:6.9.7.4+dfsg-11+deb9u3 has caused the Debian Bug report #878508, regarding imagemagick: CVE-2017-13758 to be marked as done. This means that you claim that the problem has been d

  1   2   >