Bug#440166: marked as done (installation-guide: chapter 2.1.4 missing laptop resource)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 08:53:54 +0100 with message-id <20190112085354.c0c8ac1d7dacac15d5c3a...@mailbox.org> and subject line installation-guide: chapter 2.1.4 missing laptop resource has caused the Debian Bug report #440166, regarding installation-guide: chapter 2.1.4 missing laptop re

Bug#890063: marked as done (ripperx: [INTL:de] Updated German translation)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 06:49:30 + with message-id and subject line Bug#890063: fixed in ripperx 2.8.0-2 has caused the Debian Bug report #890063, regarding ripperx: [INTL:de] Updated German translation to be marked as done. This means that you claim that the problem has been deal

Bug#853203: marked as done (ripperx FTCBFS: uses the build architecture pkg-config)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 06:49:30 + with message-id and subject line Bug#853203: fixed in ripperx 2.8.0-2 has caused the Debian Bug report #853203, regarding ripperx FTCBFS: uses the build architecture pkg-config to be marked as done. This means that you claim that the problem has

Bug#874727: marked as done (libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:00:04 -0600 with message-id and subject line has caused the Debian Bug report #874727, regarding libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults. to be marked as done. This means that you claim that the problem ha

Bug#919032: marked as done (RM: multiple [kfreebsd-amd64 kfreebsd-i386 hurd-i386] -- RoQA; Unbuildable, out of date, no rdepends)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 04:23:55 + with message-id and subject line Bug#919032: Removed package(s) from unstable has caused the Debian Bug report #919032, regarding RM: multiple [kfreebsd-amd64 kfreebsd-i386 hurd-i386] -- RoQA; Unbuildable, out of date, no rdepends to be marked as

Bug#918958: marked as done (RFS: monitorix/3.10.1-1 [ITP])

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 04:25:21 + with message-id and subject line closing RFS: monitorix/3.10.1-1 [ITP] has caused the Debian Bug report #918958, regarding RFS: monitorix/3.10.1-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#918891: marked as done (ocrmypdf: autopkgtest regression)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 01:04:48 + with message-id and subject line Bug#918891: fixed in ocrmypdf 8.0.0+dfsg-1 has caused the Debian Bug report #918891, regarding ocrmypdf: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with.

Bug#918855: marked as done (debconf: Impossible to upgrade from 1.5.59 -> 1.5.69)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:26:11 -0800 with message-id <87wona6ajw@secretsauce.net> and subject line Re: Bug#918855: debconf: Impossible to upgrade from 1.5.59 -> 1.5.69 has caused the Debian Bug report #918855, regarding debconf: Impossible to upgrade from 1.5.59 -> 1.5.69 to be m

Bug#301278: marked as done (Help page needs improvement)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:32:20 +0100 with message-id <20190111233220.78b6fb516edb54bc0ffea...@mailbox.org> and subject line [d-i partitioning] Help page needs improvement has caused the Debian Bug report #301278, regarding Help page needs improvement to be marked as done. This means

Bug#918560: marked as done (csound-manual FTBFS: IndexError: tuple index out of range)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:34:37 + with message-id and subject line Bug#918560: fixed in csound-manual 1:6.12.0~dfsg-2 has caused the Debian Bug report #918560, regarding csound-manual FTBFS: IndexError: tuple index out of range to be marked as done. This means that you claim that

Bug#918767: marked as done (rivet FTBFS with yaml-cpp 0.6.2)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:37:00 + with message-id and subject line Bug#918767: fixed in rivet 1.8.3-3 has caused the Debian Bug report #918767, regarding rivet FTBFS with yaml-cpp 0.6.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#883778: marked as done (problems building guile-2.0 on armel)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Jan 2019 01:06:28 +0200 with message-id <20190111230628.GA2487@localhost> and subject line Re: Bug#883778: problems building guile-2.0 on armel has caused the Debian Bug report #883778, regarding problems building guile-2.0 on armel to be marked as done. This means that

Bug#918772: marked as done (Fetching fails with NoSuchMethodError under Java 8 (java.nio.ByteBuffer.flip()))

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:16:09 + with message-id and subject line Bug#918772: fixed in wagon 3.3.1-1 has caused the Debian Bug report #918772, regarding Fetching fails with NoSuchMethodError under Java 8 (java.nio.ByteBuffer.flip()) to be marked as done. This means that you cla

Bug#892348: marked as done (xmlroff: Please use 'pkg-config' to find FreeType 2)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:16:19 + with message-id and subject line Bug#892348: fixed in xmlroff 0.6.2-1.4 has caused the Debian Bug report #892348, regarding xmlroff: Please use 'pkg-config' to find FreeType 2 to be marked as done. This means that you claim that the problem has b

Bug#720133: marked as done ([installation-guide] uses old release numbering scheme (7.1 is not 7.0))

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:50:32 +0100 with message-id <20190111235032.873587384f43050d1d1ef...@mailbox.org> and subject line [installation-guide] uses old release numbering scheme (7.1 is not 7.0) has caused the Debian Bug report #720133, regarding [installation-guide] uses old releas

Bug#918872: marked as done (RM: r-cran-phylobase [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures only)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:24:21 + with message-id and subject line Bug#918872: Removed package(s) from unstable has caused the Debian Bug report #918872, regarding RM: r-cran-phylobase [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures

Bug#919014: marked as done (RM: sonic-visualiser [armel] -- ROM; FTBFS)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:28:58 + with message-id and subject line Bug#919014: Removed package(s) from unstable has caused the Debian Bug report #919014, regarding RM: sonic-visualiser [armel] -- ROM; FTBFS to be marked as done. This means that you claim that the problem has been

Bug#919011: marked as done (RM: sl-modem-source -- NBS; manual cruft removal needed)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:28:48 + with message-id and subject line Bug#919011: Removed package(s) from unstable has caused the Debian Bug report #919011, regarding RM: sl-modem-source -- NBS; manual cruft removal needed to be marked as done. This means that you claim that the pro

Bug#918877: marked as done (RM: r-cran-surveillance [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures only)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:27:09 + with message-id and subject line Bug#918877: Removed package(s) from unstable has caused the Debian Bug report #918877, regarding RM: r-cran-surveillance [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectu

Bug#918874: marked as done (RM: r-cran-raster [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures only)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:26:06 + with message-id and subject line Bug#918874: Removed package(s) from unstable has caused the Debian Bug report #918874, regarding RM: r-cran-raster [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures on

Bug#887234: marked as done (python-cgcloud-core should depend on e2fsprogs explicitly)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:21:44 + with message-id and subject line Bug#918869: Removed package(s) from unstable has caused the Debian Bug report #887234, regarding python-cgcloud-core should depend on e2fsprogs explicitly to be marked as done. This means that you claim that the p

Bug#919013: marked as done (RFS: arptables/0.0.4+snapshot20181021-3 - ARP table administration)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:20:37 + with message-id and subject line closing RFS: arptables/0.0.4+snapshot20181021-3 - ARP table administration has caused the Debian Bug report #919013, regarding RFS: arptables/0.0.4+snapshot20181021-3 - ARP table administration to be marked as don

Bug#918871: marked as done (RM: python-bd2k -- ROM; No longer needed by Debian, abandoned upstream)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:23:40 + with message-id and subject line Bug#918871: Removed package(s) from unstable has caused the Debian Bug report #918871, regarding RM: python-bd2k -- ROM; No longer needed by Debian, abandoned upstream to be marked as done. This means that you cla

Bug#918869: marked as done (RM: python-cgcloud -- ROM; No longer need by Debian, abandoned upstream)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:21:37 + with message-id and subject line Bug#918869: Removed package(s) from unstable has caused the Debian Bug report #918869, regarding RM: python-cgcloud -- ROM; No longer need by Debian, abandoned upstream to be marked as done. This means that you c

Bug#918867: marked as done (RM: thunderbird [mips mipsel] -- RoQA; thunderbird does currently not build for mips/mipsel)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:21:00 + with message-id and subject line Bug#918867: Removed package(s) from unstable has caused the Debian Bug report #918867, regarding RM: thunderbird [mips mipsel] -- RoQA; thunderbird does currently not build for mips/mipsel to be marked as done. T

Bug#854556: marked as done (packages description says "someone please add a good description")

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:21:44 + with message-id and subject line Bug#918869: Removed package(s) from unstable has caused the Debian Bug report #854556, regarding packages description says "someone please add a good description" to be marked as done. This means that you claim th

Bug#918870: marked as done (RM: r-cran-luminescence [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectures only)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:22:56 + with message-id and subject line Bug#918870: Removed package(s) from unstable has caused the Debian Bug report #918870, regarding RM: r-cran-luminescence [kfreebsd-amd64 kfreebsd-i386] -- ROM; Old cruft package existing on non-released architectu

Bug#918866: marked as done (RM: birdtray [mips mipsel hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- RoQA; thunderbird does currently not build for mips/mipsel/hurd/kfreebsd)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:19:26 + with message-id and subject line Bug#918866: Removed package(s) from unstable has caused the Debian Bug report #918866, regarding RM: birdtray [mips mipsel hurd-i386 kfreebsd-amd64 kfreebsd-i386] -- RoQA; thunderbird does currently not build for

Bug#918831: marked as done (RM: python-htseq-doc -- NBS; manual cruft removal needed)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:18:17 -0500 with message-id <1874338.slf9s6VC5h@kitterma-e6430> and subject line Re: RM: python-htseq-doc -- NBS; manual cruft removal needed has caused the Debian Bug report #918831, regarding RM: python-htseq-doc -- NBS; manual cruft removal needed to be mar

Bug#918790: marked as done (RM: psi4 [mips] -- ROM; autobuilders time out)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:16:52 + with message-id and subject line Bug#918790: Removed package(s) from unstable has caused the Debian Bug report #918790, regarding RM: psi4 [mips] -- ROM; autobuilders time out to be marked as done. This means that you claim that the problem has b

Bug#918838: marked as done (RM: mldemos [armel armhf] -- NBS; no longer built on armel/armhf)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:19:12 + with message-id and subject line Bug#918838: Removed package(s) from unstable has caused the Debian Bug report #918838, regarding RM: mldemos [armel armhf] -- NBS; no longer built on armel/armhf to be marked as done. This means that you claim tha

Bug#917648: marked as done (clamav-freshclam: doesn't properly clean up temporary files, consumes all disk)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:04:58 + with message-id and subject line Bug#917648: fixed in clamav 0.101.1+dfsg-1 has caused the Debian Bug report #917648, regarding clamav-freshclam: doesn't properly clean up temporary files, consumes all disk to be marked as done. This means that

Bug#903834: marked as done (clamav-freshclam: AppArmor denies access to /proc//status)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:04:58 + with message-id and subject line Bug#903834: fixed in clamav 0.101.1+dfsg-1 has caused the Debian Bug report #903834, regarding clamav-freshclam: AppArmor denies access to /proc//status to be marked as done. This means that you claim that the pro

Bug#913020: marked as done (clamd: apparmor denials: cap net_admin, openssl.conf)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 22:04:58 + with message-id and subject line Bug#913020: fixed in clamav 0.101.1+dfsg-1 has caused the Debian Bug report #913020, regarding clamd: apparmor denials: cap net_admin, openssl.conf to be marked as done. This means that you claim that the problem

Bug#704162: marked as done (Wrong sum for GTK installer initrd.gz inside netboot.tar.gz)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:01:42 +0100 with message-id <20190111230142.978c28021d129817d4392...@mailbox.org> and subject line Wrong sum for GTK installer initrd.gz inside netboot.tar.gz has caused the Debian Bug report #704162, regarding Wrong sum for GTK installer initrd.gz inside netb

Bug#917495: marked as done (hhsuite: FTBFS ('ffsort_index' was not declared in this scope))

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 23:54:50 +0200 with message-id <20190111215450.GG17164@localhost> and subject line Fixed in 3.0~beta3+dfsg-2 has caused the Debian Bug report #917495, regarding hhsuite: FTBFS ('ffsort_index' was not declared in this scope) to be marked as done. This means that

Bug#917639: marked as done (gnome-disk-utility FTCBFS: broken fallocate check)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:50:05 + with message-id and subject line Bug#917639: fixed in gnome-disk-utility 3.30.2-3 has caused the Debian Bug report #917639, regarding gnome-disk-utility FTCBFS: broken fallocate check to be marked as done. This means that you claim that the probl

Bug#914179: marked as done (RM: weboob -- on anti harrassment team recommendation)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:45:59 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #914179, regarding RM: weboob -- on anti harrassment team recommendation to be marked as done. This means that you claim that the probl

Bug#809767: marked as done (videoob: failure to download from arte+7)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #809767, regarding videoob: failure to download from arte+7 to be marked as done. This means that you claim that the problem has been d

Bug#831609: marked as done (videoob/arte: not able to download under some configurations)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #831609, regarding videoob/arte: not able to download under some configurations to be marked as done. This means that you claim that th

Bug#751717: marked as done (python-weboob: completion script has huge impact on shell startup time)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #751717, regarding python-weboob: completion script has huge impact on shell startup time to be marked as done. This means that you cla

Bug#878991: marked as done (please drop transitional package python-weboob-core)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #878991, regarding please drop transitional package python-weboob-core to be marked as done. This means that you claim that the problem

Bug#817186: marked as done (Boobank reveals hidden password)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #817186, regarding Boobank reveals hidden password to be marked as done. This means that you claim that the problem has been dealt with

Bug#799305: marked as done ([weboob] boobank: please add support for Casden Bank)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #799305, regarding [weboob] boobank: please add support for Casden Bank to be marked as done. This means that you claim that the proble

Bug#906119: marked as done (Gratuitous sexual references)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #906119, regarding Gratuitous sexual references to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#741982: marked as done (boobank/crag module is unusable)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #741982, regarding boobank/crag module is unusable to be marked as done. This means that you claim that the problem has been dealt with

Bug#904513: marked as done (weboob: broken symlink: /usr/share/weboob/webextension-session-importer/logo.png -> ../../docs/source/_static/favicon.ico)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #904513, regarding weboob: broken symlink: /usr/share/weboob/webextension-session-importer/logo.png -> ../../docs/source/_static/favic

Bug#873642: marked as done (weboob-qt: misses dependency on python-pyqt5.qtmultimedia)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #873642, regarding weboob-qt: misses dependency on python-pyqt5.qtmultimedia to be marked as done. This means that you claim that the p

Bug#898830: marked as done (weboob-qt: qgalleroob from /usr/share/applications/qgalleroob.desktop cannot be found in $PATH)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #898830, regarding weboob-qt: qgalleroob from /usr/share/applications/qgalleroob.desktop cannot be found in $PATH to be marked as done.

Bug#808586: marked as done (weboob: network connection setting up bash completion)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #808586, regarding weboob: network connection setting up bash completion to be marked as done. This means that you claim that the probl

Bug#772357: marked as done (weboob: bashism in /bin/sh script)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #772357, regarding weboob: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has been dealt wi

Bug#746657: marked as done (weboob: boobank/bp regression when used from skrooge)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:14 + with message-id and subject line Bug#914179: Removed package(s) from unstable has caused the Debian Bug report #746657, regarding weboob: boobank/bp regression when used from skrooge to be marked as done. This means that you claim that the proble

Bug#916356: marked as done (qpsmtpd: [INTL:nl] Dutch translation of debconf messages)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:22:24 + with message-id and subject line Bug#916356: fixed in qpsmtpd 0.94-4 has caused the Debian Bug report #916356, regarding qpsmtpd: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the problem has

Bug#914121: marked as done (qpsmtpd: typo in qpsmtpd.templates)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:22:24 + with message-id and subject line Bug#914121: fixed in qpsmtpd 0.94-4 has caused the Debian Bug report #914121, regarding qpsmtpd: typo in qpsmtpd.templates to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#878340: marked as done (libmariadbclient-dev-compat: mysqlclient.pc is not visible to pkg-config)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:22:16 + with message-id and subject line Bug#878340: fixed in mariadb-10.3 1:10.3.12-1 has caused the Debian Bug report #878340, regarding libmariadbclient-dev-compat: mysqlclient.pc is not visible to pkg-config to be marked as done. This means that you

Bug#917689: marked as done (harvest-tools: FTBFS: configure: error: Cap'n Proto headers not found.)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:06:22 + with message-id and subject line Bug#917511: fixed in harvest-tools 1.3-4 has caused the Debian Bug report #917511, regarding harvest-tools: FTBFS: configure: error: Cap'n Proto headers not found. to be marked as done. This means that you claim t

Bug#917511: marked as done (harvest-tools FTBFS, "This code requires C++14. Either your compiler does not support it or it is not enabled.")

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:06:22 + with message-id and subject line Bug#917511: fixed in harvest-tools 1.3-4 has caused the Debian Bug report #917511, regarding harvest-tools FTBFS, "This code requires C++14. Either your compiler does not support it or it is not enabled." to be ma

Bug#882120: marked as done (zeitgeist: [INTL:de] Initial German translation)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:06:55 + with message-id and subject line Bug#882120: fixed in zeitgeist 1.0.1-0.3 has caused the Debian Bug report #882120, regarding zeitgeist: [INTL:de] Initial German translation to be marked as done. This means that you claim that the problem has bee

Bug#917276: marked as done (mysql-defaults and MariaDB 10.3)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 21:46:33 +0200 with message-id and subject line mysql-defaults done has caused the Debian Bug report #917276, regarding mysql-defaults and MariaDB 10.3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#918613: marked as done (ruby-rack-contrib FTBFS with ruby-rack 2.0.6-2)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:51:39 + with message-id and subject line Bug#918766: Removed package(s) from unstable has caused the Debian Bug report #918613, regarding ruby-rack-contrib FTBFS with ruby-rack 2.0.6-2 to be marked as done. This means that you claim that the problem has

Bug#918766: marked as done (RM: ruby-rack-contrib -- ROM; no uploaders, no reverse depends, delaying rails 5 transition)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:51:33 + with message-id and subject line Bug#918766: Removed package(s) from unstable has caused the Debian Bug report #918766, regarding RM: ruby-rack-contrib -- ROM; no uploaders, no reverse depends, delaying rails 5 transition to be marked as done. T

Bug#916428: marked as done (autopkgtest-virt-qemu: Fails to set up test environment when run with python3.7)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:49:04 + with message-id and subject line Bug#916428: fixed in autopkgtest 5.8 has caused the Debian Bug report #916428, regarding autopkgtest-virt-qemu: Fails to set up test environment when run with python3.7 to be marked as done. This means that you c

Bug#916499: marked as done (autopkgtest: Something™ in autopkgtest 5.7 breaks something™ in at least libhtml-formfu-perl's autopkgtests)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:49:04 + with message-id and subject line Bug#916499: fixed in autopkgtest 5.8 has caused the Debian Bug report #916499, regarding autopkgtest: Something™ in autopkgtest 5.7 breaks something™ in at least libhtml-formfu-perl's autopkgtests to be marked as

Bug#918900: marked as done (arptables: alternativ native nicht möglich)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:34:03 + with message-id and subject line Bug#918900: fixed in arptables 0.0.4+snapshot20181021-3 has caused the Debian Bug report #918900, regarding arptables: alternativ native nicht möglich to be marked as done. This means that you claim that the probl

Bug#894824: marked as done (popt FTCBFS: api-sanity-checker dependency unsatisfiable)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:22:10 + with message-id and subject line Bug#894824: fixed in popt 1.16-12 has caused the Debian Bug report #894824, regarding popt FTCBFS: api-sanity-checker dependency unsatisfiable to be marked as done. This means that you claim that the problem has b

Bug#901080: marked as done (libtest-differences-perl: t/column-headers.t fails with verbose tests)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:08:02 + with message-id and subject line Bug#901080: fixed in libtest-simple-perl 1.302156-1 has caused the Debian Bug report #901080, regarding libtest-differences-perl: t/column-headers.t fails with verbose tests to be marked as done. This means that y

Bug#918805: marked as done (ITP: suricata-update -- tool for updating Suricata rules)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:00:10 + with message-id and subject line Bug#918805: fixed in suricata-update 1.0.3-1 has caused the Debian Bug report #918805, regarding ITP: suricata-update -- tool for updating Suricata rules to be marked as done. This means that you claim that the pr

Bug#894600: marked as done (libpopt0: package priority change?)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 13:50:18 -0500 with message-id and subject line Re: Bug#894600: libpopt0: package priority change? has caused the Debian Bug report #894600, regarding libpopt0: package priority change? to be marked as done. This means that you claim that the problem has been d

Bug#885178: marked as done (python-sympy: should enhance ipython (not recommend it))

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 19:35:47 +0100 with message-id <2019083547.GA21977@localhost> and subject line this bug is closed in revision 1.3-1 has caused the Debian Bug report #885178, regarding python-sympy: should enhance ipython (not recommend it) to be marked as done. This means t

Bug#886984: marked as done (asterisk: Version 15.2 available)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:34:15 + with message-id and subject line Bug#886984: fixed in asterisk 1:16.1.1~dfsg-1 has caused the Debian Bug report #886984, regarding asterisk: Version 15.2 available to be marked as done. This means that you claim that the problem has been dealt wi

Bug#917481: marked as done (Please test Asterisk 16.1 (for Buster) in experimental)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:34:15 + with message-id and subject line Bug#917481: fixed in asterisk 1:16.1.1~dfsg-1 has caused the Debian Bug report #917481, regarding Please test Asterisk 16.1 (for Buster) in experimental to be marked as done. This means that you claim that the pro

Bug#778746: marked as done (asterisk: running /etc/init.d/asterisk restart may end up without a running asterisk)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:34:15 + with message-id and subject line Bug#778746: fixed in asterisk 1:16.1.1~dfsg-1 has caused the Debian Bug report #778746, regarding asterisk: running /etc/init.d/asterisk restart may end up without a running asterisk to be marked as done. This me

Bug#801629: marked as done (asterisk: when run with systemd, asterisk no longer defaults to realtime or allows it to be configured)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:34:15 + with message-id and subject line Bug#801629: fixed in asterisk 1:16.1.1~dfsg-1 has caused the Debian Bug report #801629, regarding asterisk: when run with systemd, asterisk no longer defaults to realtime or allows it to be configured to be marked

Bug#852368: marked as done (keepassx FTCBFS: runs tests despite DEB_BUILD_OPTIONS=nocheck)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:35:51 + with message-id and subject line Bug#852368: fixed in keepassx 2.0.3-1.1 has caused the Debian Bug report #852368, regarding keepassx FTCBFS: runs tests despite DEB_BUILD_OPTIONS=nocheck to be marked as done. This means that you claim that the pr

Bug#821392: marked as done (asterisk: Astersk take exclusive control of audio device)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 18:34:15 + with message-id and subject line Bug#821392: fixed in asterisk 1:16.1.1~dfsg-1 has caused the Debian Bug report #821392, regarding asterisk: Astersk take exclusive control of audio device to be marked as done. This means that you claim that the p

Bug#738812: marked as done (blktool: No upstream Homepage URL)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 20:06:26 +0200 with message-id <2019080625.GF17164@localhost> and subject line Fixed in 4-7 has caused the Debian Bug report #738812, regarding blktool: No upstream Homepage URL to be marked as done. This means that you claim that the problem has been dealt

Bug#918982: marked as done (libspandsp-doc: missing Breaks+Replaces: libspandsp-dev (<< 0.0.6+dfsg-1))

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:50:58 + with message-id and subject line Bug#918982: fixed in spandsp 0.0.6+dfsg-2 has caused the Debian Bug report #918982, regarding libspandsp-doc: missing Breaks+Replaces: libspandsp-dev (<< 0.0.6+dfsg-1) to be marked as done. This means that you cl

Processed: closing 826172

2019-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 826172 Bug #826172 [tahoe-lafs] tahoe-lafs: Debian initscript issues with systemd Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 826172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: Re: [pkg-lynx-maint] Bug#918945: lynx: Lynx fails to connect on some HTTPS websites

2019-01-11 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 918934 -1 Bug #918934 {Done: Axel Beckert } [lynx] lynx: Lynx fails to connect on some HTTPS websites Bug #918945 [lynx] lynx: Lynx fails to connect on some HTTPS websites Changed Bug forwarded-to-address to 'http://lists.gnu.org/archive/html/lynx-dev/20

Bug#853011: marked as done (irrlicht FTCBFS: uses the build architecture compiler)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:21:26 + with message-id and subject line Bug#853011: fixed in irrlicht 1.8.4+dfsg1-1.1 has caused the Debian Bug report #853011, regarding irrlicht FTCBFS: uses the build architecture compiler to be marked as done. This means that you claim that the prob

Bug#917128: marked as done (udev 240 breaks network interface naming)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:44:48 +0100 with message-id <8986a07e-9226-c363-e75f-298b30df1...@debian.org> and subject line Re: udev 240 breaks network interface naming has caused the Debian Bug report #917128, regarding udev 240 breaks network interface naming to be marked as done. This

Bug#918236: marked as done (ruby-prawn-svg: FTBFS in sid)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:40:07 +0100 with message-id <2019064007.GA32200@esfahan> and subject line transient bug in ruby-prawn has caused the Debian Bug report #918236, regarding ruby-prawn-svg: FTBFS in sid to be marked as done. This means that you claim that the problem has bee

Bug#918235: marked as done (ruby-prawn-icon: FTBFS in sid)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:36:51 +0100 with message-id <2019063651.GA30244@esfahan> and subject line transient bug in ruby-prawn has caused the Debian Bug report #918235, regarding ruby-prawn-icon: FTBFS in sid to be marked as done. This means that you claim that the problem has be

Bug#918605: marked as done (ruby-rspec-rails FTBFS with rails 5.2)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 17:12:19 +0100 with message-id <2019061219.GB2@esfahan> and subject line fixed with 3.8.1-2 upload has caused the Debian Bug report #918605, regarding ruby-rspec-rails FTBFS with rails 5.2 to be marked as done. This means that you claim that the problem

Bug#908162: marked as done (grub-efi-amd64-signed: cryptdisk support missing)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:52:54 + with message-id and subject line Bug#908162: fixed in grub2 2.02+dfsg1-10 has caused the Debian Bug report #908162, regarding grub-efi-amd64-signed: cryptdisk support missing to be marked as done. This means that you claim that the problem has be

Bug#841889: marked as done (grub-pc: ucf prompt that wants to change nothing except remove admin-defined config)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:52:54 + with message-id and subject line Bug#812574: fixed in grub2 2.02+dfsg1-10 has caused the Debian Bug report #812574, regarding grub-pc: ucf prompt that wants to change nothing except remove admin-defined config to be marked as done. This means th

Bug#812574: marked as done (grub-pc: wants to overwrite admin configuration on each upgrade)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:52:54 + with message-id and subject line Bug#812574: fixed in grub2 2.02+dfsg1-10 has caused the Debian Bug report #812574, regarding grub-pc: wants to overwrite admin configuration on each upgrade to be marked as done. This means that you claim that the

Bug#776450: marked as done (grub-xen-host: does not work with PVH)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:52:54 + with message-id and subject line Bug#776450: fixed in grub2 2.02+dfsg1-10 has caused the Debian Bug report #776450, regarding grub-xen-host: does not work with PVH to be marked as done. This means that you claim that the problem has been dealt wi

Bug#918602: marked as done (ruby-haml FTBFS with rails 5.2)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 16:41:56 +0100 with message-id <2019054156.GA32130@esfahan> and subject line fixed with upload of ruby-haml/5.0.4-1 has caused the Debian Bug report #918602, regarding ruby-haml FTBFS with rails 5.2 to be marked as done. This means that you claim that the pr

Bug#892930: marked as done (tlsh FTCBFS: unsatisfiable cross build-depends)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:35:14 + with message-id and subject line Bug#892930: fixed in tlsh 3.4.4+20151206-1.1 has caused the Debian Bug report #892930, regarding tlsh FTCBFS: unsatisfiable cross build-depends to be marked as done. This means that you claim that the problem has

Bug#909296: marked as done (libical3: Enable GObject Introspection and Vala .vapi file generation)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 10:35:54 -0500 with message-id and subject line Re: Bug#909296: libical3: Enable GObject Introspection and Vala .vapi file generation has caused the Debian Bug report #909296, regarding libical3: Enable GObject Introspection and Vala .vapi file generation to b

Bug#918020: marked as done ([INTL:sv] Swedish strings for zfs-linux debconf)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:00:53 + with message-id and subject line Bug#918020: fixed in zfs-linux 0.7.12-2 has caused the Debian Bug report #918020, regarding [INTL:sv] Swedish strings for zfs-linux debconf to be marked as done. This means that you claim that the problem has been

Bug#915831: marked as done (zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 15:00:53 + with message-id and subject line Bug#915831: fixed in zfs-linux 0.7.12-2 has caused the Debian Bug report #915831, regarding zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure to be marked as done. This means that you claim that t

Bug#918544: marked as done (python-numpy: Breaks on the wrong version of python-astropy)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 14:55:50 + with message-id and subject line Bug#918544: fixed in python-numpy 1:1.16.0~rc2-2 has caused the Debian Bug report #918544, regarding python-numpy: Breaks on the wrong version of python-astropy to be marked as done. This means that you claim that

Bug#918251: marked as done (d-shlibs: devlibs error: There is no package matching [libsvm3-dev] and noone provides it)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 13:34:25 + with message-id and subject line Bug#918251: fixed in d-shlibs 0.84 has caused the Debian Bug report #918251, regarding d-shlibs: devlibs error: There is no package matching [libsvm3-dev] and noone provides it to be marked as done. This means th

Bug#915886: marked as done (zfs-dkms: module FTBFS for 4.18.0-3-amd64: NR_FILE_PAGES in either node_stat_item or zone_stat_item: NOT FOUND)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 13:35:59 + with message-id <2019033559.GA23073@Asuna> and subject line Re: zfs-dkms: module FTBFS for 4.18.0-3-amd64: NR_FILE_PAGES in either node_stat_item or zone_stat_item: NOT FOUND has caused the Debian Bug report #915886, regarding zfs-dkms: module

Bug#918705: marked as done (URL parsing fails with NoSuchMethodError on Java 8)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 13:35:09 + with message-id and subject line Bug#918705: fixed in httpcomponents-client 4.5.6-2 has caused the Debian Bug report #918705, regarding URL parsing fails with NoSuchMethodError on Java 8 to be marked as done. This means that you claim that the pr

Bug#916299: marked as done (nmu: postgresql-11_11.1-1)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 14:18:46 +0100 with message-id <2019031846.ga21...@msg.df7cb.de> and subject line Re: Bug#916299: postgresql-11: starts with error after upgrade from stretch to buster has caused the Debian Bug report #916299, regarding nmu: postgresql-11_11.1-1 to be marked

Bug#912360: marked as done (postgresql-client-11: depends on libedit2 is not installed correctly)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 14:16:26 +0100 with message-id <2019031626.gc16...@msg.df7cb.de> and subject line Re: [Pkg-postgresql-public] Bug#912360: postgresql-client-11: depends on libedit2 is not installed correctly has caused the Debian Bug report #912360, regarding postgresql-clie

Bug#916885: marked as done (pass-tomb: depends on kcov which is not in testing)

2019-01-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Jan 2019 13:05:43 + with message-id and subject line Bug#916885: fixed in pass-tomb 1.1-4 has caused the Debian Bug report #916885, regarding pass-tomb: depends on kcov which is not in testing to be marked as done. This means that you claim that the problem has been

  1   2   >