Bug#906505: marked as done (qlandkartegt: FTBFS in buster/sid (unable to find string literal operator))

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:54:52 + with message-id and subject line Bug#906515: Removed package(s) from unstable has caused the Debian Bug report #906505, regarding qlandkartegt: FTBFS in buster/sid (unable to find string literal operator) to be marked as done. This means that

Bug#832426: marked as done (sipwitch FTBFS on mips64el - incorrect symbols)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:58 + with message-id and subject line Bug#906802: Removed package(s) from unstable has caused the Debian Bug report #832426, regarding sipwitch FTBFS on mips64el - incorrect symbols to be marked as done. This means that you claim that the problem has

Bug#906582: marked as done (RM: attal-themes -- RoQA; Unmaintained; Upstream dead; Affected by Qt4 Removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:06 + with message-id and subject line Bug#906582: Removed package(s) from unstable has caused the Debian Bug report #906582, regarding RM: attal-themes -- RoQA; Unmaintained; Upstream dead; Affected by Qt4 Removal to be marked as done. This means

Bug#906251: marked as done (RM: kde4libs -- ROM; manual decruft needed)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:54:24 + with message-id and subject line Bug#906251: Removed package(s) from unstable has caused the Debian Bug report #906251, regarding RM: kde4libs -- ROM; manual decruft needed to be marked as done. This means that you claim that the problem has

Bug#900468: marked as done (attal: Should this package be removed?)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #900468, regarding attal: Should this package be removed? to be marked as done. This means that you claim that the problem has been

Bug#906563: marked as done (RM: libcsp -- ROM; unused package, buggy)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:14 + with message-id and subject line Bug#906563: Removed package(s) from unstable has caused the Debian Bug report #906563, regarding RM: libcsp -- ROM; unused package, buggy to be marked as done. This means that you claim that the problem has been

Bug#906581: marked as done (RM: attal -- RoQA; RC-buggy; Unmaintained; Upstream dead; Affected by Qt4 Removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:39 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #906581, regarding RM: attal -- RoQA; RC-buggy; Unmaintained; Upstream dead; Affected by Qt4 Removal to be marked as done. This means

Bug#906515: marked as done (RM: qlandkartegt -- ROM; FTBFS with Qt 5.11, superseded by QMapShack)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:54:48 + with message-id and subject line Bug#906515: Removed package(s) from unstable has caused the Debian Bug report #906515, regarding RM: qlandkartegt -- ROM; FTBFS with Qt 5.11, superseded by QMapShack to be marked as done. This means that you

Bug#889275: marked as done (sipwitch-cgi is empty)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:58 + with message-id and subject line Bug#906802: Removed package(s) from unstable has caused the Debian Bug report #889275, regarding sipwitch-cgi is empty to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#906802: marked as done (RM: sipwitch -- ROM; unused, possibly dead upstream)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:54 + with message-id and subject line Bug#906802: Removed package(s) from unstable has caused the Debian Bug report #906802, regarding RM: sipwitch -- ROM; unused, possibly dead upstream to be marked as done. This means that you claim that the

Bug#906704: marked as done (RM: camlpdf [armel] -- RoQA; FTBFS on bytecode architectures)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:31 + with message-id and subject line Bug#906704: Removed package(s) from unstable has caused the Debian Bug report #906704, regarding RM: camlpdf [armel] -- RoQA; FTBFS on bytecode architectures to be marked as done. This means that you claim that

Bug#874827: marked as done ([attal] Future Qt4 removal from Buster)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #874827, regarding [attal] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#900479: marked as done (attal-themes: Should this package be removed?)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:56:10 + with message-id and subject line Bug#906582: Removed package(s) from unstable has caused the Debian Bug report #900479, regarding attal-themes: Should this package be removed? to be marked as done. This means that you claim that the problem has

Bug#726208: marked as done (attal: missing icon entry in menu file Jessie Release Goal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #726208, regarding attal: missing icon entry in menu file Jessie Release Goal to be marked as done. This means that you claim that the

Bug#868376: marked as done (attal: homepage no longer exists)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #868376, regarding attal: homepage no longer exists to be marked as done. This means that you claim that the problem has been dealt

Bug#831094: marked as done (attal: FTBFS with GCC 6: cmath:568:33: error: 'FP_NAN' was not declared in this scope)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #831094, regarding attal: FTBFS with GCC 6: cmath:568:33: error: 'FP_NAN' was not declared in this scope to be marked as done. This

Bug#843012: marked as done (libcsp: CVE-2016-8596 CVE-2016-8597 CVE-2016-8598)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:17 + with message-id and subject line Bug#906563: Removed package(s) from unstable has caused the Debian Bug report #843012, regarding libcsp: CVE-2016-8596 CVE-2016-8597 CVE-2016-8598 to be marked as done. This means that you claim that the problem

Bug#811232: marked as done (FTBFS with parallel build: cannot find -lAttalAi)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:55:46 + with message-id and subject line Bug#906581: Removed package(s) from unstable has caused the Debian Bug report #811232, regarding FTBFS with parallel build: cannot find -lAttalAi to be marked as done. This means that you claim that the problem

Bug#906177: marked as done (RM: libxatracker2 libxatracker-dev [armel arm64 armhf mips mips64el mipsel ppc64el s390x] -- NBS; needs manual cruft removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:46:10 + with message-id and subject line Bug#906177: Removed package(s) from unstable has caused the Debian Bug report #906177, regarding RM: libxatracker2 libxatracker-dev [armel arm64 armhf mips mips64el mipsel ppc64el s390x] -- NBS; needs manual

Bug#896249: marked as done (python-tau: tau fails to import)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:44:36 + with message-id and subject line Bug#905956: Removed package(s) from unstable has caused the Debian Bug report #896249, regarding python-tau: tau fails to import to be marked as done. This means that you claim that the problem has been dealt

Bug#531433: marked as done (let qrfcview read gzipped files too)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:45:13 + with message-id and subject line Bug#906121: Removed package(s) from unstable has caused the Debian Bug report #531433, regarding let qrfcview read gzipped files too to be marked as done. This means that you claim that the problem has been dealt

Bug#907621: marked as done (llvm-3.8: Compiler Error for wrong conversion in LLVM/include/llvm/IR/ValueMap.h while building KLEE)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #907621, regarding llvm-3.8: Compiler Error for wrong conversion in LLVM/include/llvm/IR/ValueMap.h while building KLEE to be marked

Bug#789963: marked as done (qrfcview: please make the build reproducible)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:45:13 + with message-id and subject line Bug#906121: Removed package(s) from unstable has caused the Debian Bug report #789963, regarding qrfcview: please make the build reproducible to be marked as done. This means that you claim that the problem has

Bug#906121: marked as done (RM: qrfcview -- RoQA; Unmaintained; Upstream dead; Affected by Qt4 Removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:45:06 + with message-id and subject line Bug#906121: Removed package(s) from unstable has caused the Debian Bug report #906121, regarding RM: qrfcview -- RoQA; Unmaintained; Upstream dead; Affected by Qt4 Removal to be marked as done. This means that

Bug#905956: marked as done (RM: tau -- ROM; package is broken and outdated, new versions harder to package)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:44:30 + with message-id and subject line Bug#905956: Removed package(s) from unstable has caused the Debian Bug report #905956, regarding RM: tau -- ROM; package is broken and outdated, new versions harder to package to be marked as done. This means

Bug#875143: marked as done ([qrfcview] Future Qt4 removal from Buster)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:45:13 + with message-id and subject line Bug#906121: Removed package(s) from unstable has caused the Debian Bug report #875143, regarding [qrfcview] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#887161: marked as done (llvm-toolchain-3.8: keep out of testing)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #887161, regarding llvm-toolchain-3.8: keep out of testing to be marked as done. This means that you claim that the problem has been

Bug#885856: marked as done (llvm-toolchain-3.8: ExecutionEngine/MCJIT/remote/test-global-init-nonzero-remote.ll stalls on armhf)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #885856, regarding llvm-toolchain-3.8: ExecutionEngine/MCJIT/remote/test-global-init-nonzero-remote.ll stalls on armhf to be marked as

Bug#897004: marked as done (pypibrowser: Should package pypibrowser be removed?)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:42:07 + with message-id and subject line Bug#905804: Removed package(s) from unstable has caused the Debian Bug report #897004, regarding pypibrowser: Should package pypibrowser be removed? to be marked as done. This means that you claim that the

Bug#628443: marked as done (qrfcview: Bad encoding of some characters in the document outline panel)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:45:13 + with message-id and subject line Bug#906121: Removed package(s) from unstable has caused the Debian Bug report #628443, regarding qrfcview: Bad encoding of some characters in the document outline panel to be marked as done. This means that you

Bug#874242: marked as done (libclang1-3.8 is wrongly marked Multi-Arch: same)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #874242, regarding libclang1-3.8 is wrongly marked Multi-Arch: same to be marked as done. This means that you claim that the problem

Bug#905863: marked as done (RM: bugsx -- RoQA; RC_buggy, unmaintained, dead upstream, unused)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:58 + with message-id and subject line Bug#905863: Removed package(s) from unstable has caused the Debian Bug report #905863, regarding RM: bugsx -- RoQA; RC_buggy, unmaintained, dead upstream, unused to be marked as done. This means that you claim

Bug#905861: marked as done (RM: pavuk -- RoQA; dead upstream, RC-buggy, alternatives exist)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:28 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #905861, regarding RM: pavuk -- RoQA; dead upstream, RC-buggy, alternatives exist to be marked as done. This means that you claim that

Bug#884327: marked as done (clang-format-3.8: man page contains spurious error text)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #884327, regarding clang-format-3.8: man page contains spurious error text to be marked as done. This means that you claim that the

Bug#849646: marked as done (ImportError: No module named lldb.embedded_interpreter)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #849646, regarding ImportError: No module named lldb.embedded_interpreter to be marked as done. This means that you claim that the

Bug#857680: marked as done (llvm-3.8-examples: broken symlinks: /usr/share/doc/llvm-3.8-examples/Makefile.* -> ../../../lib/llvm-3.8/build/Makefile.*)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #857680, regarding llvm-3.8-examples: broken symlinks: /usr/share/doc/llvm-3.8-examples/Makefile.* ->

Bug#905804: marked as done (RM: pypibrowser -- RoQA; Unmaintained; Dead Upstream; Affected by Qt4 Removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:42:02 + with message-id and subject line Bug#905804: Removed package(s) from unstable has caused the Debian Bug report #905804, regarding RM: pypibrowser -- RoQA; Unmaintained; Dead Upstream; Affected by Qt4 Removal to be marked as done. This means

Bug#835823: marked as done (Polly's imath assumes little-endian)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #835823, regarding Polly's imath assumes little-endian to be marked as done. This means that you claim that the problem has been dealt

Bug#848191: marked as done (clang-3.8: scan-view-3.8 can't find python module ScanView in its path)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #848191, regarding clang-3.8: scan-view-3.8 can't find python module ScanView in its path to be marked as done. This means that you

Bug#873331: marked as done (RM: llvm-toolchain-3.8 -- ROM; Too many version of llvm-toolchain in unstable)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:42:42 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #873331, regarding RM: llvm-toolchain-3.8 -- ROM; Too many version of llvm-toolchain in unstable to be marked as done. This means

Bug#817292: marked as done (bugsx: Removal of dh_desktop)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:44:03 + with message-id and subject line Bug#905863: Removed package(s) from unstable has caused the Debian Bug report #817292, regarding bugsx: Removal of dh_desktop to be marked as done. This means that you claim that the problem has been dealt with.

Bug#826289: marked as done (build a python3-lldb-3.8 package)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #826289, regarding build a python3-lldb-3.8 package to be marked as done. This means that you claim that the problem has been dealt

Bug#825155: marked as done (incomplete libclang shared library)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #825155, regarding incomplete libclang shared library to be marked as done. This means that you claim that the problem has been dealt

Bug#871011: marked as done (clang-3.8: incompatible with libstdc++-7-dev)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #871011, regarding clang-3.8: incompatible with libstdc++-7-dev to be marked as done. This means that you claim that the problem has

Bug#859540: marked as done (pavuk: Please migrate to openssl1.1 in Buster)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:36 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #859540, regarding pavuk: Please migrate to openssl1.1 in Buster to be marked as done. This means that you claim that the problem has

Bug#829441: marked as done (Package cant be installed for multiple archs (eg. amd64 and i386))

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #829441, regarding Package cant be installed for multiple archs (eg. amd64 and i386) to be marked as done. This means that you claim

Bug#841009: marked as done (liblldb-3.8-dev: missing symlinks)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #841009, regarding liblldb-3.8-dev: missing symlinks to be marked as done. This means that you claim that the problem has been dealt

Bug#837533: marked as done (libllvm3.8: Debian's LLVM segfaults when Debian's rustc tries to compile a "stdcall" declaration on arm64)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #837533, regarding libllvm3.8: Debian's LLVM segfaults when Debian's rustc tries to compile a "stdcall" declaration on arm64 to be

Bug#840894: marked as done (llvm-3.8: lli-3.8 man page contains fakeroot error)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #840894, regarding llvm-3.8: lli-3.8 man page contains fakeroot error to be marked as done. This means that you claim that the problem

Bug#840208: marked as done (llvm-toolchain-3.8: FTBFS when golang-go is installe)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #840208, regarding llvm-toolchain-3.8: FTBFS when golang-go is installe to be marked as done. This means that you claim that the

Bug#833563: marked as done (libfuzzer-3.8-dev: illegal hardware instruction)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #833563, regarding libfuzzer-3.8-dev: illegal hardware instruction to be marked as done. This means that you claim that the problem

Bug#830850: marked as done (clang-3.8: 'sys/cdefs.h' file not found on armhf)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #830850, regarding clang-3.8: 'sys/cdefs.h' file not found on armhf to be marked as done. This means that you claim that the problem

Bug#798111: marked as done (Illegal instruction after compiling some code)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #798111, regarding Illegal instruction after compiling some code to be marked as done. This means that you claim that the problem has

Bug#758776: marked as done (please build a python3-clang package)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #758776, regarding please build a python3-clang package to be marked as done. This means that you claim that the problem has been

Bug#809180: marked as done (clang-3.8 is tuned for k8)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #809180, regarding clang-3.8 is tuned for k8 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#819278: marked as done (llvm-toolchain-3.8: Build not reliable)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #819278, regarding llvm-toolchain-3.8: Build not reliable to be marked as done. This means that you claim that the problem has been

Bug#817238: marked as done (llvm-toolchain-3.8: Sanitizers (asan, tsan) should be packaged into a dedicated package)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #817238, regarding llvm-toolchain-3.8: Sanitizers (asan, tsan) should be packaged into a dedicated package to be marked as done. This

Bug#212201: marked as done (pavuk: segfaults almost immediately with -X)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:36 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #212201, regarding pavuk: segfaults almost immediately with -X to be marked as done. This means that you claim that the problem has

Bug#232008: marked as done (pavuk: segfaults sometimes)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:36 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #232008, regarding pavuk: segfaults sometimes to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#155539: marked as done (pavuk: please consider building pavuk-tiny)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:36 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #155539, regarding pavuk: please consider building pavuk-tiny to be marked as done. This means that you claim that the problem has

Bug#479567: marked as done (pavuk: Segfault during operation)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:36 + with message-id and subject line Bug#905861: Removed package(s) from unstable has caused the Debian Bug report #479567, regarding pavuk: Segfault during operation to be marked as done. This means that you claim that the problem has been dealt

Bug#751789: marked as done (llvm-toolchain-3.4: Ship compiler-rt library as a separate package)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #751789, regarding llvm-toolchain-3.4: Ship compiler-rt library as a separate package to be marked as done. This means that you claim

Bug#811287: marked as done (Clang: should pull libomp5 AND/OR libomp-dev package for OpenMP support)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #811287, regarding Clang: should pull libomp5 AND/OR libomp-dev package for OpenMP support to be marked as done. This means that you

Bug#747213: marked as done (llvm-toolchain-3.4: Build with the hardening flags)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:43:06 + with message-id and subject line Bug#873331: Removed package(s) from unstable has caused the Debian Bug report #747213, regarding llvm-toolchain-3.4: Build with the hardening flags to be marked as done. This means that you claim that the problem

Bug#905799: marked as done (RM: tk8.5 -- ROQA; obsolete)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:39:39 + with message-id and subject line Bug#905799: Removed package(s) from unstable has caused the Debian Bug report #905799, regarding RM: tk8.5 -- ROQA; obsolete to be marked as done. This means that you claim that the problem has been dealt with.

Bug#641185: marked as done (tk8.5: Various Tk-based programs only display menu text in upper-left corner of screen)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:39:48 + with message-id and subject line Bug#905799: Removed package(s) from unstable has caused the Debian Bug report #641185, regarding tk8.5: Various Tk-based programs only display menu text in upper-left corner of screen to be marked as done. This

Bug#652612: marked as done (dependencies are not strict enough : upgrade of tk broke rubytk)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:39:48 + with message-id and subject line Bug#905799: Removed package(s) from unstable has caused the Debian Bug report #652612, regarding dependencies are not strict enough : upgrade of tk broke rubytk to be marked as done. This means that you claim

Bug#896085: marked as done (tk8.5: Time to remove from Debian)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:39:48 + with message-id and subject line Bug#905799: Removed package(s) from unstable has caused the Debian Bug report #896085, regarding tk8.5: Time to remove from Debian to be marked as done. This means that you claim that the problem has been dealt

Bug#605041: marked as done (git-gui: commit message box doesn't respond to enter (only return))

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:39:48 + with message-id and subject line Bug#905799: Removed package(s) from unstable has caused the Debian Bug report #605041, regarding git-gui: commit message box doesn't respond to enter (only return) to be marked as done. This means that you claim

Bug#906803: marked as done (RM: cipux,cipux-dog,cipux-object,cipux-passwd,cipux-rbac,cipux-rbac-simple,cipux-rpc,cipux-rpc-client,cipux-storage,cipux-task,module-build-cipux -- ROM; unused, dead upstr

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:38:50 + with message-id and subject line Bug#905444: Removed package(s) from unstable has caused the Debian Bug report #906803, regarding RM:

Bug#824281: marked as done (Updating the cipux-rpc-client Uploaders list)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:38:50 + with message-id and subject line Bug#905444: Removed package(s) from unstable has caused the Debian Bug report #824281, regarding Updating the cipux-rpc-client Uploaders list to be marked as done. This means that you claim that the problem has

Bug#905444: marked as done (RM: cipux-rpc-client -- RoQA; dead upstream and unused)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:38:46 + with message-id and subject line Bug#905444: Removed package(s) from unstable has caused the Debian Bug report #905444, regarding RM: cipux-rpc-client -- RoQA; dead upstream and unused to be marked as done. This means that you claim that the

Bug#905410: marked as done (RM: gotestyourself -- ROM; NPOASR; upstream rename)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 01:38:04 -0400 with message-id <2492496.UEsqZZ34Ge@kitterma-e6430> and subject line Re: RM: gotestyourself -- ROM; NPOASR; upstream rename has caused the Debian Bug report #905410, regarding RM: gotestyourself -- ROM; NPOASR; upstream rename to be marked as

Bug#899472: marked as done (cipux-rpc-client: Invalid maintainer address cipux-de...@lists.alioth.debian.org)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:38:50 + with message-id and subject line Bug#905444: Removed package(s) from unstable has caused the Debian Bug report #899472, regarding cipux-rpc-client: Invalid maintainer address cipux-de...@lists.alioth.debian.org to be marked as done. This means

Bug#863694: marked as done (Updating the zendframework Uploaders list)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:58 + with message-id and subject line Bug#904565: Removed package(s) from unstable has caused the Debian Bug report #863694, regarding Updating the zendframework Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#909866: marked as done (ooniprobe: (Build-) Depends on vanished package python-txtorcon)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:36:25 + with message-id and subject line Bug#905211: Removed package(s) from unstable has caused the Debian Bug report #909866, regarding ooniprobe: (Build-) Depends on vanished package python-txtorcon to be marked as done. This means that you claim

Bug#827695: marked as done (zendframework: Rename zend-framework in Ubuntu to allow for a package sync)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:58 + with message-id and subject line Bug#904565: Removed package(s) from unstable has caused the Debian Bug report #827695, regarding zendframework: Rename zend-framework in Ubuntu to allow for a package sync to be marked as done. This means that

Bug#755649: marked as done (python-django-threadedcomments: Please ensure it works with Django 1.7)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:55 + with message-id and subject line Bug#904929: Removed package(s) from unstable has caused the Debian Bug report #755649, regarding python-django-threadedcomments: Please ensure it works with Django 1.7 to be marked as done. This means that you

Bug#896352: marked as done (python-django-threadedcomments: threadedcomments fails to import)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:55 + with message-id and subject line Bug#904929: Removed package(s) from unstable has caused the Debian Bug report #896352, regarding python-django-threadedcomments: threadedcomments fails to import to be marked as done. This means that you claim

Bug#905211: marked as done (RM: ooniprobe -- ROM; not easily maintained; too many js deps)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:36:20 + with message-id and subject line Bug#905211: Removed package(s) from unstable has caused the Debian Bug report #905211, regarding RM: ooniprobe -- ROM; not easily maintained; too many js deps to be marked as done. This means that you claim that

Bug#884245: marked as done (gmediaserver: FTBFS against upnp 1.8)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:32:13 + with message-id and subject line Bug#904833: Removed package(s) from unstable has caused the Debian Bug report #884245, regarding gmediaserver: FTBFS against upnp 1.8 to be marked as done. This means that you claim that the problem has been

Bug#905348: marked as done (RM: pymca [armel mips mips64el mipsel ppc64el s390x] -- ANAIS; it nows depends transitively on pyopencl which is not available everywhere)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:36:59 + with message-id and subject line Bug#905348: Removed package(s) from unstable has caused the Debian Bug report #905348, regarding RM: pymca [armel mips mips64el mipsel ppc64el s390x] -- ANAIS; it nows depends transitively on pyopencl which is

Bug#911546: marked as done (RM: letodms -- RoQA; unmaintained, dead upstream, depends on obsolete libs)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:33:17 + with message-id and subject line Bug#911546: Removed package(s) from unstable has caused the Debian Bug report #911546, regarding RM: letodms -- RoQA; unmaintained, dead upstream, depends on obsolete libs to be marked as done. This means that

Bug#878730: marked as done (O: gmediaserver -- UPnP Mediaserver)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:32:13 + with message-id and subject line Bug#904833: Removed package(s) from unstable has caused the Debian Bug report #878730, regarding O: gmediaserver -- UPnP Mediaserver to be marked as done. This means that you claim that the problem has been dealt

Bug#904865: marked as done (RM: promoe -- RoQA; Orphaned; Upstream development stalled; Affected by Qt4 Removal)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:22 + with message-id and subject line Bug#904865: Removed package(s) from unstable has caused the Debian Bug report #904865, regarding RM: promoe -- RoQA; Orphaned; Upstream development stalled; Affected by Qt4 Removal to be marked as done. This

Bug#660537: marked as done (Support Matroska Media Containers)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:32:13 + with message-id and subject line Bug#904833: Removed package(s) from unstable has caused the Debian Bug report #660537, regarding Support Matroska Media Containers to be marked as done. This means that you claim that the problem has been dealt

Bug#863716: marked as done (zendframework package is missing in stretch)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:58 + with message-id and subject line Bug#904565: Removed package(s) from unstable has caused the Debian Bug report #863716, regarding zendframework package is missing in stretch to be marked as done. This means that you claim that the problem has

Bug#761833: marked as done (O: promoe -- GUI client for XMMS2)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:27 + with message-id and subject line Bug#904865: Removed package(s) from unstable has caused the Debian Bug report #761833, regarding O: promoe -- GUI client for XMMS2 to be marked as done. This means that you claim that the problem has been dealt

Bug#818315: marked as done (letodms: please don't use "if ! dbc_go" in your maintainer scripts)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:33:23 + with message-id and subject line Bug#911546: Removed package(s) from unstable has caused the Debian Bug report #818315, regarding letodms: please don't use "if ! dbc_go" in your maintainer scripts to be marked as done. This means that you claim

Bug#827698: marked as done (Depends on zendframework, but zendframework is going away)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:32 + with message-id and subject line Bug#911546: Removed package(s) from unstable has caused the Debian Bug report #827698, regarding Depends on zendframework, but zendframework is going away to be marked as done. This means that you claim that the

Bug#831418: marked as done (EOL: not to be released with Stretch)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:58 + with message-id and subject line Bug#904565: Removed package(s) from unstable has caused the Debian Bug report #831418, regarding EOL: not to be released with Stretch to be marked as done. This means that you claim that the problem has been

Bug#901537: marked as done (ooniprobe: FTBFS: ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy))

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:36:25 + with message-id and subject line Bug#905211: Removed package(s) from unstable has caused the Debian Bug report #901537, regarding ooniprobe: FTBFS: ERROR: test_send_packet_with_answer (ooni.tests.test_txscapy.TestTxScapy) to be marked as done.

Bug#904833: marked as done (RM: gmediaserver -- RoQA; unmaintained upstream and in Debian)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:32:07 + with message-id and subject line Bug#904833: Removed package(s) from unstable has caused the Debian Bug report #904833, regarding RM: gmediaserver -- RoQA; unmaintained upstream and in Debian to be marked as done. This means that you claim that

Bug#780964: marked as done (letodms indexer doesn't work (php file not found))

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:33:23 + with message-id and subject line Bug#911546: Removed package(s) from unstable has caused the Debian Bug report #780964, regarding letodms indexer doesn't work (php file not found) to be marked as done. This means that you claim that the problem

Bug#801935: marked as done (python-django-threadedcomments: Fails to build from source with Django 1.8)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:55 + with message-id and subject line Bug#904929: Removed package(s) from unstable has caused the Debian Bug report #801935, regarding python-django-threadedcomments: Fails to build from source with Django 1.8 to be marked as done. This means that

Bug#904565: marked as done (RM: zendframework -- ROM; Deprecated upstream, superseded by php-zend-*)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:34:52 + with message-id and subject line Bug#904565: Removed package(s) from unstable has caused the Debian Bug report #904565, regarding RM: zendframework -- ROM; Deprecated upstream, superseded by php-zend-* to be marked as done. This means that you

Bug#875117: marked as done ([promoe] Future Qt4 removal from Buster)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:27 + with message-id and subject line Bug#904865: Removed package(s) from unstable has caused the Debian Bug report #875117, regarding [promoe] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#838487: marked as done (letodms: LetoDMS upstream is dead - transition to SeedDMS?)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:33:23 + with message-id and subject line Bug#911546: Removed package(s) from unstable has caused the Debian Bug report #838487, regarding letodms: LetoDMS upstream is dead - transition to SeedDMS? to be marked as done. This means that you claim that the

Bug#887379: marked as done (gmediaserver FTCBFS: perl build dependency unsatisfiable)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:32:13 + with message-id and subject line Bug#904833: Removed package(s) from unstable has caused the Debian Bug report #887379, regarding gmediaserver FTCBFS: perl build dependency unsatisfiable to be marked as done. This means that you claim that the

Bug#904929: marked as done (RM: python-django-threadedcomments -- RoQA; unmaintained, RC buggy, non-functional)

2018-10-30 Thread Debian Bug Tracking System
Your message dated Wed, 31 Oct 2018 05:35:50 + with message-id and subject line Bug#904929: Removed package(s) from unstable has caused the Debian Bug report #904929, regarding RM: python-django-threadedcomments -- RoQA; unmaintained, RC buggy, non-functional to be marked as done. This

  1   2   3   4   >