Bug#962137: marked as done (FTBFS when building architecture independent packages only)

Your message dated Thu, 04 Jun 2020 06:33:39 + with message-id and subject line Bug#962137: fixed in nghttp2 1.41.0-2 has caused the Debian Bug report #962137, regarding FTBFS when building architecture independent packages only to be marked as done. This means that you claim that the problem

Bug#962136: marked as done (FTBFS on i386 because of .la files)

Your message dated Thu, 04 Jun 2020 06:33:39 + with message-id and subject line Bug#962136: fixed in nghttp2 1.41.0-2 has caused the Debian Bug report #962136, regarding FTBFS on i386 because of .la files to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#946057: marked as done (xmoto-data: Replace dependence on ttf-dejavu-core by fonts-dejavu-core)

Your message dated Thu, 04 Jun 2020 04:48:40 + with message-id and subject line Bug#946057: fixed in xmoto 0.6.0+repack-1 has caused the Debian Bug report #946057, regarding xmoto-data: Replace dependence on ttf-dejavu-core by fonts-dejavu-core to be marked as done. This means that you claim

Processed: Forcemerge #962060 & #962156

Processing commands for cont...@bugs.debian.org: > forcemerge 962060 962156 Bug #962060 {Done: Bas Couwenberg } [src:josm] josm: java.lang.NoClassDefFoundError: Could not initialize class org.openstreetmap.josm.data.cache.JCSCacheManager Bug #962156 [src:josm] josm: Could not initialize class o

Bug#946463: marked as done (sysdig: specific filter produces "BUG: unable to handle kernel NULL pointer dereference at...")

Your message dated Thu, 04 Jun 2020 03:34:12 + with message-id and subject line Bug#946463: fixed in sysdig 0.26.7-1 has caused the Debian Bug report #946463, regarding sysdig: specific filter produces "BUG: unable to handle kernel NULL pointer dereference at..." to be marked as done. This m

Bug#958643: marked as done (sysdig: crash the whole machine and disables login after reboot by just installing package)

Your message dated Thu, 04 Jun 2020 03:34:13 + with message-id and subject line Bug#958643: fixed in sysdig 0.26.7-1 has caused the Debian Bug report #958643, regarding sysdig: crash the whole machine and disables login after reboot by just installing package to be marked as done. This means

Bug#955279: marked as done (sysdig: undefined symbol: _ZN4grpc13ClientContextC1Ev)

Your message dated Thu, 04 Jun 2020 03:34:13 + with message-id and subject line Bug#955279: fixed in sysdig 0.26.7-1 has caused the Debian Bug report #955279, regarding sysdig: undefined symbol: _ZN4grpc13ClientContextC1Ev to be marked as done. This means that you claim that the problem has b

Bug#945443: marked as done (git-svn fails with "error: git-svn died of signal 11")

Your message dated Thu, 04 Jun 2020 03:05:13 + with message-id and subject line Bug#945443: fixed in subversion 1.14.0-1 has caused the Debian Bug report #945443, regarding git-svn fails with "error: git-svn died of signal 11" to be marked as done. This means that you claim that the problem h

Bug#577118: marked as done (subversion: Doesn't escape argument on editor invocations)

Your message dated Thu, 04 Jun 2020 03:05:13 + with message-id and subject line Bug#577118: fixed in subversion 1.14.0-1 has caused the Debian Bug report #577118, regarding subversion: Doesn't escape argument on editor invocations to be marked as done. This means that you claim that the probl

Bug#938578: marked as done (subversion: Python2 removal in sid/bullseye)

Your message dated Thu, 04 Jun 2020 03:05:13 + with message-id and subject line Bug#938578: fixed in subversion 1.14.0-1 has caused the Debian Bug report #938578, regarding subversion: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#956921: marked as done (subversion: Debian patch last-changed-date-charset has an error leak)

Your message dated Thu, 04 Jun 2020 03:05:13 + with message-id and subject line Bug#956921: fixed in subversion 1.14.0-1 has caused the Debian Bug report #956921, regarding subversion: Debian patch last-changed-date-charset has an error leak to be marked as done. This means that you claim tha

Bug#960812: marked as done (sxid: Please add Recommends for mailx | mailutils)

Your message dated Thu, 04 Jun 2020 03:05:18 + with message-id and subject line Bug#960812: fixed in sxid 4.20130802-3 has caused the Debian Bug report #960812, regarding sxid: Please add Recommends for mailx | mailutils to be marked as done. This means that you claim that the problem has bee

Bug#739790: marked as done (please provide a python3-subversion package)

Your message dated Thu, 04 Jun 2020 03:05:13 + with message-id and subject line Bug#739790: fixed in subversion 1.14.0-1 has caused the Debian Bug report #739790, regarding please provide a python3-subversion package to be marked as done. This means that you claim that the problem has been de

Bug#959767: marked as done (wfmath: Please update symbols files for recent gcc on s390x)

Your message dated Thu, 04 Jun 2020 01:34:24 + with message-id and subject line Bug#959767: fixed in wfmath 1.0.2+dfsg1-7 has caused the Debian Bug report #959767, regarding wfmath: Please update symbols files for recent gcc on s390x to be marked as done. This means that you claim that the pr

Bug#957931: marked as done (wfmath: ftbfs with GCC-10)

Your message dated Thu, 04 Jun 2020 01:34:24 + with message-id and subject line Bug#957931: fixed in wfmath 1.0.2+dfsg1-7 has caused the Debian Bug report #957931, regarding wfmath: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#906434: marked as done (alex: Changes needed to bootstrap? (riscv64))

Your message dated Thu, 04 Jun 2020 01:33:39 + with message-id and subject line Bug#906434: fixed in alex 3.2.5-1 has caused the Debian Bug report #906434, regarding alex: Changes needed to bootstrap? (riscv64) to be marked as done. This means that you claim that the problem has been dealt wi

Bug#650762: marked as done (lintian: Please support an UNPACKDIR option)

Your message dated Wed, 3 Jun 2020 18:24:30 -0700 with message-id and subject line lintian: Please support an UNPACKDIR option has caused the Debian Bug report #650762, regarding lintian: Please support an UNPACKDIR option to be marked as done. This means that you claim that the problem has been

Processed: closing 870479

Processing commands for cont...@bugs.debian.org: > close 870479 Bug #870479 [roundcube] Installation of roundcube fails with Maria DB Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 870479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87047

Bug#803634: marked as done (dep5-copyright-license-name-not-unique false positive for same license with different copyrights and files)

Your message dated Wed, 3 Jun 2020 17:56:31 -0700 with message-id and subject line lintian: false positive for same license with different copyrights and files has caused the Debian Bug report #803634, regarding dep5-copyright-license-name-not-unique false positive for same license with differe

Bug#962128: marked as done (mtdev: Please package new upstream release (1.1.6))

Your message dated Thu, 04 Jun 2020 00:19:46 + with message-id and subject line Bug#962128: fixed in mtdev 1.1.6-1 has caused the Debian Bug report #962128, regarding mtdev: Please package new upstream release (1.1.6) to be marked as done. This means that you claim that the problem has been d

Bug#923438: marked as done (tinc: breaks after upgrading libssl1.1 to v1.1.1b-1)

Your message dated Wed, 03 Jun 2020 23:35:12 + with message-id and subject line Bug#923438: fixed in tinc 1.1~pre17-1.2 has caused the Debian Bug report #923438, regarding tinc: breaks after upgrading libssl1.1 to v1.1.1b-1 to be marked as done. This means that you claim that the problem has

Bug#962098: marked as done (RM: python3.7, superseded by python3.8)

Your message dated Wed, 03 Jun 2020 22:05:55 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #962098, regarding RM: python3.7, superseded by python3.8 to be marked as done. This means that you claim that the problem has been dea

Bug#954417: marked as done (python3.7: FTBFS since openssl 1.1.1e)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #954417, regarding python3.7: FTBFS since openssl 1.1.1e to be marked as done. This means that you claim that the problem has been deal

Bug#946581: marked as done (python3.7: ssl module can't load system CA certificates)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #946581, regarding python3.7: ssl module can't load system CA certificates to be marked as done. This means that you claim that the pro

Bug#952503: marked as done (Breaking change introduced in python3.7 3.7.6 breaks python-bleach)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #952503, regarding Breaking change introduced in python3.7 3.7.6 breaks python-bleach to be marked as done. This means that you claim t

Bug#951029: marked as done (Please document unexpected behaviour in pathlib.Path('.').glob('*/') - trailing slash matches regular files)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #951029, regarding Please document unexpected behaviour in pathlib.Path('.').glob('*/') - trailing slash matches regular files to be ma

Bug#949679: marked as done (defines preprocessor symbols reserved for the application)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #949679, regarding defines preprocessor symbols reserved for the application to be marked as done. This means that you claim that the p

Bug#948178: marked as done (python3-config forces no-pie)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #948178, regarding python3-config forces no-pie to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#953152: marked as done (ctypes: TypeError: item 1 in _argtypes_ passes a union by value, which is unsupported)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #953152, regarding ctypes: TypeError: item 1 in _argtypes_ passes a union by value, which is unsupported to be marked as done. This me

Bug#944364: marked as done (dpkg: ldconfig is not invoked for Depends or even Pre-Depends)

Your message dated Wed, 03 Jun 2020 22:06:05 + with message-id and subject line Bug#962098: Removed package(s) from unstable has caused the Debian Bug report #944364, regarding dpkg: ldconfig is not invoked for Depends or even Pre-Depends to be marked as done. This means that you claim that t

Bug#961812: marked as done (RM: tarantool-lts -- ROM; obsolete)

Your message dated Wed, 03 Jun 2020 21:59:59 + with message-id and subject line Bug#961812: Removed package(s) from unstable has caused the Debian Bug report #961812, regarding RM: tarantool-lts -- ROM; obsolete to be marked as done. This means that you claim that the problem has been dealt w

Bug#444323: marked as done (pidgin-encryption: Removal of trusted buddy keys doesn't seems to work)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #444323, regarding pidgin-encryption: Removal of trusted buddy keys doesn't seems to work to be marked as done. This means that you cla

Bug#396836: marked as done (gaim-encryption: Segfault on bad known_keys content)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #396836, regarding gaim-encryption: Segfault on bad known_keys content to be marked as done. This means that you claim that the problem

Bug#961751: marked as done (RM: libusbtc08 -- RoQA; RC-buggy, current versions no longer distribute source)

Your message dated Wed, 03 Jun 2020 21:59:33 + with message-id and subject line Bug#961751: Removed package(s) from unstable has caused the Debian Bug report #961751, regarding RM: libusbtc08 -- RoQA; RC-buggy, current versions no longer distribute source to be marked as done. This means tha

Bug#961941: marked as done (RM: gmetric4j -- ROM; No longer used, low popcon)

Your message dated Wed, 03 Jun 2020 22:02:51 + with message-id and subject line Bug#961941: Removed package(s) from unstable has caused the Debian Bug report #961941, regarding RM: gmetric4j -- ROM; No longer used, low popcon to be marked as done. This means that you claim that the problem ha

Bug#557581: marked as done (pidgin-encryption: Key exchange fails rendering this plugin useless.)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #557581, regarding pidgin-encryption: Key exchange fails rendering this plugin useless. to be marked as done. This means that you claim

Bug#961868: marked as done (RM: broccoli -- ROM; deprecated)

Your message dated Wed, 03 Jun 2020 22:01:25 + with message-id and subject line Bug#961868: Removed package(s) from unstable has caused the Debian Bug report #961868, regarding RM: broccoli -- ROM; deprecated to be marked as done. This means that you claim that the problem has been dealt with

Bug#744796: marked as done ([ pidgin-encryption] Non resolved dependencies on shared library "/usr/lib/pidgin/encrypt.so")

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #744796, regarding [ pidgin-encryption] Non resolved dependencies on shared library "/usr/lib/pidgin/encrypt.so" to be marked as done.

Bug#500551: marked as done (pidgin: crashes when opening IM window for buddy for which logging is disabled.)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #500551, regarding pidgin: crashes when opening IM window for buddy for which logging is disabled. to be marked as done. This means th

Bug#961871: marked as done (RM: broccoli-ruby -- ROM; deprecated)

Your message dated Wed, 03 Jun 2020 22:02:06 + with message-id and subject line Bug#961871: Removed package(s) from unstable has caused the Debian Bug report #961871, regarding RM: broccoli-ruby -- ROM; deprecated to be marked as done. This means that you claim that the problem has been dealt

Bug#961719: marked as done (RM: pbcopper [armel armhf i386 mipsel] -- NBS; no longer supports 32bit architectures)

Your message dated Wed, 03 Jun 2020 21:58:45 + with message-id and subject line Bug#961719: Removed package(s) from unstable has caused the Debian Bug report #961719, regarding RM: pbcopper [armel armhf i386 mipsel] -- NBS; no longer supports 32bit architectures to be marked as done. This me

Bug#961854: marked as done (RM: iptables-optimizer -- RoQA; Depends on Python 2, dead upstream, unmaintained)

Your message dated Wed, 03 Jun 2020 22:01:04 + with message-id and subject line Bug#961854: Removed package(s) from unstable has caused the Debian Bug report #961854, regarding RM: iptables-optimizer -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means t

Bug#959682: marked as done (gmetric4j: diff for NMU version 1.0.10-0.1)

Your message dated Wed, 03 Jun 2020 22:02:54 + with message-id and subject line Bug#961941: Removed package(s) from unstable has caused the Debian Bug report #959682, regarding gmetric4j: diff for NMU version 1.0.10-0.1 to be marked as done. This means that you claim that the problem has been

Bug#962033: marked as done (RM: pybloomfiltermmap -- RoQA; Depends on Python 2, dead upstream, no reverse deps)

Your message dated Wed, 03 Jun 2020 22:03:10 + with message-id and subject line Bug#962033: Removed package(s) from unstable has caused the Debian Bug report #962033, regarding RM: pybloomfiltermmap -- RoQA; Depends on Python 2, dead upstream, no reverse deps to be marked as done. This means

Bug#961840: marked as done (RM: node-diffie-hellman -- ROM; unmaintained upstream)

Your message dated Wed, 03 Jun 2020 22:00:44 + with message-id and subject line Bug#961840: Removed package(s) from unstable has caused the Debian Bug report #961840, regarding RM: node-diffie-hellman -- ROM; unmaintained upstream to be marked as done. This means that you claim that the probl

Bug#961749: marked as done (RM: xenomai -- RoQA; RC-buggy, orphaned, missed two stable releases)

Your message dated Wed, 03 Jun 2020 21:59:04 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #961749, regarding RM: xenomai -- RoQA; RC-buggy, orphaned, missed two stable releases to be marked as done. This means that you claim

Bug#961824: marked as done (RM: filemanager-actions -- RoQA; RC-buggy, unmaintained)

Your message dated Wed, 03 Jun 2020 22:00:23 + with message-id and subject line Bug#961824: Removed package(s) from unstable has caused the Debian Bug report #961824, regarding RM: filemanager-actions -- RoQA; RC-buggy, unmaintained to be marked as done. This means that you claim that the pro

Bug#961099: marked as done (broccoli-python FTCBFS: uninstallable python Build-Depends)

Your message dated Wed, 03 Jun 2020 22:01:48 + with message-id and subject line Bug#961870: Removed package(s) from unstable has caused the Debian Bug report #961099, regarding broccoli-python FTCBFS: uninstallable python Build-Depends to be marked as done. This means that you claim that the

Bug#937392: marked as done (pybloomfiltermmap: Python2 removal in sid/bullseye)

Your message dated Wed, 03 Jun 2020 22:03:13 + with message-id and subject line Bug#962033: Removed package(s) from unstable has caused the Debian Bug report #937392, regarding pybloomfiltermmap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#943064: marked as done (iptables-optimizer: Python2 removal in sid/bullseye)

Your message dated Wed, 03 Jun 2020 22:01:07 + with message-id and subject line Bug#961854: Removed package(s) from unstable has caused the Debian Bug report #943064, regarding iptables-optimizer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#961920: marked as done (RM: pidgin-encryption -- ROM; abandoned upstream)

Your message dated Wed, 03 Jun 2020 22:02:27 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #961920, regarding RM: pidgin-encryption -- ROM; abandoned upstream to be marked as done. This means that you claim that the problem ha

Bug#491792: marked as done (pidgin-encryption: Pidgin crashes with segfault when sending/receiving messages)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #491792, regarding pidgin-encryption: Pidgin crashes with segfault when sending/receiving messages to be marked as done. This means th

Bug#899195: marked as done (RFA: pidgin-encryption -- pidgin plugin that provides transparent encryption)

Your message dated Wed, 03 Jun 2020 22:02:33 + with message-id and subject line Bug#961920: Removed package(s) from unstable has caused the Debian Bug report #899195, regarding RFA: pidgin-encryption -- pidgin plugin that provides transparent encryption to be marked as done. This means that

Bug#961870: marked as done (RM: broccoli-python -- ROM; deprecated)

Your message dated Wed, 03 Jun 2020 22:01:45 + with message-id and subject line Bug#961870: Removed package(s) from unstable has caused the Debian Bug report #961870, regarding RM: broccoli-python -- ROM; deprecated to be marked as done. This means that you claim that the problem has been dea

Bug#811980: marked as done (libusbtc08: FTBFS with GCC 6: symbol changes)

Your message dated Wed, 03 Jun 2020 21:59:39 + with message-id and subject line Bug#961751: Removed package(s) from unstable has caused the Debian Bug report #811980, regarding libusbtc08: FTBFS with GCC 6: symbol changes to be marked as done. This means that you claim that the problem has be

Bug#951717: marked as done (broccoli-ruby: suppor for multiple Ruby versions is broken)

Your message dated Wed, 03 Jun 2020 22:02:09 + with message-id and subject line Bug#961871: Removed package(s) from unstable has caused the Debian Bug report #951717, regarding broccoli-ruby: suppor for multiple Ruby versions is broken to be marked as done. This means that you claim that the

Bug#925453: marked as done (xenomai-kernel-source: ships patches for old kernel)

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #925453, regarding xenomai-kernel-source: ships patches for old kernel to be marked as done. This means that you claim that the problem

Bug#814950: marked as done (xenomai-kernel-source: Incomplete package description)

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #814950, regarding xenomai-kernel-source: Incomplete package description to be marked as done. This means that you claim that the probl

Bug#925451: marked as done (xenomai-kernel-source: depends on kernel-package, which will not be in buster)

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #925451, regarding xenomai-kernel-source: depends on kernel-package, which will not be in buster to be marked as done. This means that

Bug#922129: marked as done (filemanager-actions: Incomplete debian/copyright?)

Your message dated Wed, 03 Jun 2020 22:00:26 + with message-id and subject line Bug#961824: Removed package(s) from unstable has caused the Debian Bug report #922129, regarding filemanager-actions: Incomplete debian/copyright? to be marked as done. This means that you claim that the problem h

Bug#813470: marked as done (O: xenomai -- Real-time development framework for the Linux kernel)

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #813470, regarding O: xenomai -- Real-time development framework for the Linux kernel to be marked as done. This means that you claim t

Bug#947520: marked as done (filemanager-actions: build-depends on deprecated gnome-doc-utils)

Your message dated Wed, 03 Jun 2020 22:00:26 + with message-id and subject line Bug#961824: Removed package(s) from unstable has caused the Debian Bug report #947520, regarding filemanager-actions: build-depends on deprecated gnome-doc-utils to be marked as done. This means that you claim tha

Bug#922702: marked as done (xenomai-kernel-source: the upstream release eol (from 2014))

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #922702, regarding xenomai-kernel-source: the upstream release eol (from 2014) to be marked as done. This means that you claim that the

Bug#907770: marked as done (tarantool-lts-modules: The package names in the Recommends are incorrect)

Your message dated Wed, 03 Jun 2020 22:00:04 + with message-id and subject line Bug#961812: Removed package(s) from unstable has caused the Debian Bug report #907770, regarding tarantool-lts-modules: The package names in the Recommends are incorrect to be marked as done. This means that you

Bug#860939: marked as done (node-diffie-hellman: Please clarify security concerns)

Your message dated Wed, 03 Jun 2020 22:00:48 + with message-id and subject line Bug#961840: Removed package(s) from unstable has caused the Debian Bug report #860939, regarding node-diffie-hellman: Please clarify security concerns to be marked as done. This means that you claim that the probl

Bug#743457: marked as done (xenomai: Please enable build for armhf)

Your message dated Wed, 03 Jun 2020 21:59:14 + with message-id and subject line Bug#961749: Removed package(s) from unstable has caused the Debian Bug report #743457, regarding xenomai: Please enable build for armhf to be marked as done. This means that you claim that the problem has been dea

Bug#961689: marked as done (orville-write: please remove alternatives usage for write(1))

Your message dated Wed, 03 Jun 2020 21:57:25 + with message-id and subject line Bug#961688: Removed package(s) from unstable has caused the Debian Bug report #961689, regarding orville-write: please remove alternatives usage for write(1) to be marked as done. This means that you claim that th

Bug#957648: marked as done (orville-write: ftbfs with GCC-10)

Your message dated Wed, 03 Jun 2020 21:57:25 + with message-id and subject line Bug#961688: Removed package(s) from unstable has caused the Debian Bug report #957648, regarding orville-write: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#961688: marked as done (RM: orville-write -- RoQA; not useful anymore)

Your message dated Wed, 03 Jun 2020 21:57:17 + with message-id and subject line Bug#961688: Removed package(s) from unstable has caused the Debian Bug report #961688, regarding RM: orville-write -- RoQA; not useful anymore to be marked as done. This means that you claim that the problem has b

Bug#940980: marked as done (clang-7: ICE while building pocl on mips*el)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #940980, regarding clang-7: ICE while building pocl on mips*el to be marked as done. This means that you claim that the problem has bee

Bug#936958: marked as done (llvm-toolchain-7: Python2 removal in sid/bullseye)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #936958, regarding llvm-toolchain-7: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#922275: marked as done (libomp-7-dev: Feature Request To Have libomp-7-dev Install Symlink /usr/lib//libomp.so)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #922275, regarding libomp-7-dev: Feature Request To Have libomp-7-dev Install Symlink /usr/lib//libomp.so to be marked as done. This m

Bug#928693: marked as done (clang-7: Using --coverage causes "/usr/bin/ld: …: hidden symbol `llvm_gcda_end_file'" error)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #928693, regarding clang-7: Using --coverage causes "/usr/bin/ld: …: hidden symbol `llvm_gcda_end_file'" error to be marked as done. T

Bug#931029: marked as done (lldb-7: Uses Python 2 instead of Python 3)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #931029, regarding lldb-7: Uses Python 2 instead of Python 3 to be marked as done. This means that you claim that the problem has been

Bug#947438: marked as done (RM: llvm-toolchain-7 -- ROM; Less versions of llvm, the better)

Your message dated Wed, 03 Jun 2020 21:55:11 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #947438, regarding RM: llvm-toolchain-7 -- ROM; Less versions of llvm, the better to be marked as done. This means that you claim that

Bug#926478: marked as done (clang-tidy-7: Missng manpage)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #926478, regarding clang-tidy-7: Missng manpage to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#934408: marked as done (sys::fs::directory_iterator is broken on armel/armhf/mips)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #934408, regarding sys::fs::directory_iterator is broken on armel/armhf/mips to be marked as done. This means that you claim that the p

Bug#914097: marked as done (libomp5-7: not multiarch compatible)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #914097, regarding libomp5-7: not multiarch compatible to be marked as done. This means that you claim that the problem has been dealt

Bug#920872: marked as done (libomp not multiarch-installable)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #920872, regarding libomp not multiarch-installable to be marked as done. This means that you claim that the problem has been dealt wit

Bug#920347: marked as done (llvm-toolchain-7: Move libraries in /usr/lib/llvm-X/lib/)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #920347, regarding llvm-toolchain-7: Move libraries in /usr/lib/llvm-X/lib/ to be marked as done. This means that you claim that the p

Bug#916945: marked as done (llvm-toolchain-7: unicode non free license)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #916945, regarding llvm-toolchain-7: unicode non free license to be marked as done. This means that you claim that the problem has been

Bug#915156: marked as done (libclang1-7 fails to coinstall)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #915156, regarding libclang1-7 fails to coinstall to be marked as done. This means that you claim that the problem has been dealt with.

Bug#914201: marked as done (clang-7: Passing double to isnan() triggers -Wconversion)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #914201, regarding clang-7: Passing double to isnan() triggers -Wconversion to be marked as done. This means that you claim that the pr

Bug#914042: marked as done (qtcreator's clang code model appears to be broken with kit = clang)

Your message dated Wed, 03 Jun 2020 21:55:28 + with message-id and subject line Bug#947438: Removed package(s) from unstable has caused the Debian Bug report #914042, regarding qtcreator's clang code model appears to be broken with kit = clang to be marked as done. This means that you claim t

Bug#700309: marked as done (wotsap: Wotsap can't read latest .wot files from http://wot.christoph-egger.org/)

Your message dated Wed, 03 Jun 2020 21:44:39 + with message-id and subject line Bug#945746: Removed package(s) from unstable has caused the Debian Bug report #700309, regarding wotsap: Wotsap can't read latest .wot files from http://wot.christoph-egger.org/ to be marked as done. This means t

Bug#945746: marked as done (RM: wotsap -- removal triggered by the Python2 removal)

Your message dated Wed, 03 Jun 2020 21:44:30 + with message-id and subject line Bug#945746: Removed package(s) from unstable has caused the Debian Bug report #945746, regarding RM: wotsap -- removal triggered by the Python2 removal to be marked as done. This means that you claim that the prob

Bug#796012: marked as done (suggested URLs for wotsap database outdated)

Your message dated Wed, 03 Jun 2020 21:44:39 + with message-id and subject line Bug#945746: Removed package(s) from unstable has caused the Debian Bug report #796012, regarding suggested URLs for wotsap database outdated to be marked as done. This means that you claim that the problem has bee

Bug#800134: marked as done (wotsap: should handle 64-bit key IDs gracefully)

Your message dated Wed, 03 Jun 2020 21:44:39 + with message-id and subject line Bug#945746: Removed package(s) from unstable has caused the Debian Bug report #800134, regarding wotsap: should handle 64-bit key IDs gracefully to be marked as done. This means that you claim that the problem has

Bug#959792: marked as done (libmozjs-68-0 is confused about the soname)

Your message dated Wed, 03 Jun 2020 21:42:07 + with message-id and subject line Bug#959792: fixed in mozjs68 68.9.0-1 has caused the Debian Bug report #959792, regarding libmozjs-68-0 is confused about the soname to be marked as done. This means that you claim that the problem has been dealt

Bug#959144: marked as done (mozjs68: Build-depends on cargo and rustc but doesn't actually use it)

Your message dated Wed, 03 Jun 2020 21:42:07 + with message-id and subject line Bug#959144: fixed in mozjs68 68.9.0-1 has caused the Debian Bug report #959144, regarding mozjs68: Build-depends on cargo and rustc but doesn't actually use it to be marked as done. This means that you claim that

Bug#961933: marked as done (odt2txt: autopkgtest failure: file: command not found)

Your message dated Wed, 03 Jun 2020 21:42:21 + with message-id and subject line Bug#961933: fixed in odt2txt 0.5-4 has caused the Debian Bug report #961933, regarding odt2txt: autopkgtest failure: file: command not found to be marked as done. This means that you claim that the problem has bee

Bug#956734: marked as done (gnucobol FTCBFS: lots of AC_RUN_IFELSE)

Your message dated Wed, 3 Jun 2020 20:51:16 +0200 with message-id <20200603185116.ga25...@alf.mars> and subject line Re: gnucobol FTCBFS: lots of AC_RUN_IFELSE has caused the Debian Bug report #956734, regarding gnucobol FTCBFS: lots of AC_RUN_IFELSE to be marked as done. This means that you claim

Bug#962060: marked as done (josm: java.lang.NoClassDefFoundError: Could not initialize class org.openstreetmap.josm.data.cache.JCSCacheManager)

Your message dated Wed, 03 Jun 2020 20:36:11 + with message-id and subject line Bug#962060: fixed in josm 0.0.svn16538+dfsg-3 has caused the Debian Bug report #962060, regarding josm: java.lang.NoClassDefFoundError: Could not initialize class org.openstreetmap.josm.data.cache.JCSCacheManager

Bug#960296: marked as done (bbpager FTCBFS: broken, outdated, embedded copy of PKG_CHECK_MODULES)

Your message dated Wed, 03 Jun 2020 20:34:52 + with message-id and subject line Bug#960296: fixed in bbpager 0.4.7-8 has caused the Debian Bug report #960296, regarding bbpager FTCBFS: broken, outdated, embedded copy of PKG_CHECK_MODULES to be marked as done. This means that you claim that th

Bug#835997: marked as done (python-ldns broken: AttributeError: 'module' object has no attribute 'LDNS_RR_CLASS_IN')

Your message dated Wed, 3 Jun 2020 22:07:09 +0200 with message-id <20200603200709.GA2299491@bartik> and subject line Re: Bug#835997: python-ldns broken: AttributeError: 'module' object has no attribute 'LDNS_RR_CLASS_IN' has caused the Debian Bug report #835997, regarding python-ldns broken: Attri

Bug#962116: marked as done (Updating the emboss Uploaders list)

Your message dated Wed, 03 Jun 2020 19:48:38 + with message-id and subject line Bug#962116: fixed in emboss 6.6.0+dfsg-8 has caused the Debian Bug report #962116, regarding Updating the emboss Uploaders list to be marked as done. This means that you claim that the problem has been dealt with.

Bug#962115: marked as done (Updating the sibsim4 Uploaders list)

Your message dated Wed, 03 Jun 2020 19:21:14 + with message-id and subject line Bug#962115: fixed in sibsim4 0.20-5 has caused the Debian Bug report #962115, regarding Updating the sibsim4 Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#962113: marked as done (Updating the gff2aplot Uploaders list)

Your message dated Wed, 03 Jun 2020 19:19:47 + with message-id and subject line Bug#962113: fixed in gff2aplot 2.0-12 has caused the Debian Bug report #962113, regarding Updating the gff2aplot Uploaders list to be marked as done. This means that you claim that the problem has been dealt with.

Bug#865434: marked as done (mtpolicyd: missing dependencies for default configuration)

Your message dated Wed, 03 Jun 2020 13:56:31 -0400 with message-id <5961422.Ly6H3sn4mU@sk-desktop> and subject line Re: mtpolicyd: missing dependencies for default configuration has caused the Debian Bug report #865434, regarding mtpolicyd: missing dependencies for default configuration to be marke

Bug#962076: marked as done (clementine: Clementine crash)

Your message dated Wed, 3 Jun 2020 14:33:13 -0300 with message-id and subject line has caused the Debian Bug report #962076, regarding clementine: Clementine crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your respon

  1   2   >