Bug#885025: marked as done (gerbera: FTBFS against upnp 1.8.3)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 23:19:20 + with message-id and subject line Bug#885025: fixed in gerbera 1.1.0+dfsg-3 has caused the Debian Bug report #885025, regarding gerbera: FTBFS against upnp 1.8.3 to be marked as done. This means that you claim that the problem has been dealt

Bug#913067: marked as done (bibletime: transition to sword 1.8.1)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 07:47:26 +0700 with message-id and subject line bibletime built against 1.8.1+dfsg has caused the Debian Bug report #913067, regarding bibletime: transition to sword 1.8.1 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: closing 913587

2018-11-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 913587 Bug #913587 [grub-common] Drop obsolete /etc/default/grub.d/init-select.cfg Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 913587:

Bug#911704: marked as done (keymapper: depends on obsolete yapps2-runtime)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 04:19:12 + with message-id and subject line Bug#911704: fixed in keymapper 0.5.3-11 has caused the Debian Bug report #911704, regarding keymapper: depends on obsolete yapps2-runtime to be marked as done. This means that you claim that the problem has been

Bug#913554: marked as done (rdfind FTBFS on 32bit: error: call of overloaded 'update(std::streamsize, char [4096])' is ambiguous)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 02:40:38 + with message-id and subject line Bug#913554: fixed in rdfind 1.4.1-1 has caused the Debian Bug report #913554, regarding rdfind FTBFS on 32bit: error: call of overloaded 'update(std::streamsize, char [4096])' is ambiguous to be marked as done.

Bug#913101: marked as done (RFS: lebiniou-data/3.27-1 -- datafiles for Le Biniou)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 01:37:30 +0100 with message-id <20181113003730.pc5tr7qgbdfql...@angband.pl> and subject line Re: Bug#913101: RFS: lebiniou-data/3.27-1 -- datafiles for Le Biniou has caused the Debian Bug report #913101, regarding RFS: lebiniou-data/3.27-1 -- datafiles for Le

Bug#913522: marked as done (libgpiod FTBFS on 32bit: symbol differences)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 04:04:09 + with message-id and subject line Bug#913522: fixed in libgpiod 1.2-1 has caused the Debian Bug report #913522, regarding libgpiod FTBFS on 32bit: symbol differences to be marked as done. This means that you claim that the problem has been dealt

Bug#913070: marked as done (xiphos does not run on testing - sword 1.8.1 transition needed)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 06:04:06 + with message-id and subject line Bug#913070: fixed in xiphos 4.1.0+dfsg1-1 has caused the Debian Bug report #913070, regarding xiphos does not run on testing - sword 1.8.1 transition needed to be marked as done. This means that you claim that

Bug#913100: marked as done (RFS: lebiniou/3.27-1 -- displays images that evolve with sound)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 01:33:27 +0100 with message-id <20181113003327.vpsnfhuqgbztg...@angband.pl> and subject line Re: Bug#913100: RFS: lebiniou/3.27-1 -- displays images that evolve with sound has caused the Debian Bug report #913100, regarding RFS: lebiniou/3.27-1 -- displays

Bug#913591: marked as done (mkl-dnn: binary-all/binary-any FTBFS)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 04:34:30 + with message-id and subject line Bug#913591: fixed in mkl-dnn 0.17~rc-2 has caused the Debian Bug report #913591, regarding mkl-dnn: binary-all/binary-any FTBFS to be marked as done. This means that you claim that the problem has been dealt

Bug#900710: marked as done (very out of date manpage)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 08:41:46 + with message-id and subject line Bug#900710: fixed in kdeconnect 1.3.3-1 has caused the Debian Bug report #900710, regarding very out of date manpage to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#902324: marked as done (RFS: zeyple/1.2.2-3 [ITP])

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 10:24:47 + with message-id and subject line closing RFS: zeyple/1.2.2-3 [ITP] has caused the Debian Bug report #902324, regarding RFS: zeyple/1.2.2-3 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#913402: marked as done (tomcat8 FTBFS: error: incompatible types: Object cannot be converted)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 10:19:27 + with message-id and subject line Bug#913402: fixed in tomcat8 8.5.35-2 has caused the Debian Bug report #913402, regarding tomcat8 FTBFS: error: incompatible types: Object cannot be converted to be marked as done. This means that you claim that

Bug#852307: marked as done (bcolz: test_leftover_ptr_with_statement_create_open fails on big endian)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 10:34:00 + with message-id and subject line Bug#852307: fixed in bcolz 1.2.1+ds2-1 has caused the Debian Bug report #852307, regarding bcolz: test_leftover_ptr_with_statement_create_open fails on big endian to be marked as done. This means that you claim

Bug#903727: marked as done (ITP: perl6-zef -- Perl 6 package manager)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 10:49:42 +0200 with message-id <20181112084942.GS18621@localhost> and subject line perl6-zef is now in unstable has caused the Debian Bug report #903727, regarding ITP: perl6-zef -- Perl 6 package manager to be marked as done. This means that you claim that the

Bug#854725: marked as done (pbuilder: Failed extracting the source (cause: dpkg-source: -x needs exactly one argument, the .dsc))

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 09:49:43 + with message-id and subject line Bug#854725: fixed in pbuilder 0.230.1 has caused the Debian Bug report #854725, regarding pbuilder: Failed extracting the source (cause: dpkg-source: -x needs exactly one argument, the .dsc) to be marked as done.

Bug#913405: marked as done (seafile-gui: Undefined symbol error in seafile-applet)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:04:08 + with message-id and subject line Bug#913405: fixed in seafile 6.2.5-3 has caused the Debian Bug report #913405, regarding seafile-gui: Undefined symbol error in seafile-applet to be marked as done. This means that you claim that the problem has

Bug#913555: marked as done (libsearpc: seaf-cli from seafile-cli fails with pysearpc.errors.NetworkError)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:04:02 + with message-id and subject line Bug#913555: fixed in libsearpc 3.1.0-3 has caused the Debian Bug report #913555, regarding libsearpc: seaf-cli from seafile-cli fails with pysearpc.errors.NetworkError to be marked as done. This means that you

Bug#898472: marked as done (hunspell: needlessly linked with ncurses)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Tue, 13 Nov 2018 07:19:30 + with message-id and subject line Bug#898472: fixed in hunspell 1.6.2-2 has caused the Debian Bug report #898472, regarding hunspell: needlessly linked with ncurses to be marked as done. This means that you claim that the problem has been dealt

Bug#912845: marked as done (evolution: --express option faulted on Debian Stretch, although inlcuded on man page)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 13:34:09 + with message-id and subject line Bug#912845: fixed in evolution 3.30.2-1 has caused the Debian Bug report #912845, regarding evolution: --express option faulted on Debian Stretch, although inlcuded on man page to be marked as done. This means

Bug#912374: marked as done (apt: [INTL:nb] Norwegian Bokmål translation of po file update)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:34:00 + with message-id and subject line Bug#912374: fixed in apt 1.8.0~alpha1 has caused the Debian Bug report #912374, regarding apt: [INTL:nb] Norwegian Bokmål translation of po file update to be marked as done. This means that you claim that the

Bug#913478: marked as done (nova-placement-api not creating user placement in keystone)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:21:36 + with message-id and subject line Bug#913478: fixed in nova 2:18.0.3-3 has caused the Debian Bug report #913478, regarding nova-placement-api not creating user placement in keystone to be marked as done. This means that you claim that the problem

Bug#783920: marked as done (atlas: FTBFS on arm64 in Jessie)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 14:40:10 +0100 with message-id <1542030010.25772.19.ca...@debian.org> and subject line Re: atlas: FTBFS on arm64 in Jessie has caused the Debian Bug report #783920, regarding atlas: FTBFS on arm64 in Jessie to be marked as done. This means that you claim that

Bug#912563: marked as done (libwmf-config --cflags no longer includes required freetype2 flags)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:19:24 + with message-id and subject line Bug#912563: fixed in libwmf 0.2.8.4-14 has caused the Debian Bug report #912563, regarding libwmf-config --cflags no longer includes required freetype2 flags to be marked as done. This means that you claim that

Bug#911090: marked as done (libapt-pkg5.0: incompatible with apt/stretch)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:34:00 + with message-id and subject line Bug#911090: fixed in apt 1.8.0~alpha1 has caused the Debian Bug report #911090, regarding libapt-pkg5.0: incompatible with apt/stretch to be marked as done. This means that you claim that the problem has been

Bug#910941: marked as done (apt-get changelog uses insecure HTTP for Debian)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:34:00 + with message-id and subject line Bug#910941: fixed in apt 1.8.0~alpha1 has caused the Debian Bug report #910941, regarding apt-get changelog uses insecure HTTP for Debian to be marked as done. This means that you claim that the problem has been

Bug#912021: marked as done (apt: [INTL:nl] Dutch po file for the apt package)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 11:34:00 + with message-id and subject line Bug#912021: fixed in apt 1.8.0~alpha1 has caused the Debian Bug report #912021, regarding apt: [INTL:nl] Dutch po file for the apt package to be marked as done. This means that you claim that the problem has been

Bug#911159: marked as done (please stop building the frama-c GUI)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:20:10 + with message-id and subject line Bug#911159: fixed in frama-c 20171101+sulfur+dfsg-2 has caused the Debian Bug report #911159, regarding please stop building the frama-c GUI to be marked as done. This means that you claim that the problem has

Bug#912992: marked as done (cinder-common should configure glance_api_servers via debconf)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:49:26 + with message-id and subject line Bug#912992: fixed in cinder 2:13.0.1-1 has caused the Debian Bug report #912992, regarding cinder-common should configure glance_api_servers via debconf to be marked as done. This means that you claim that the

Bug#912991: marked as done (cinder-common should configure my_ip directive in /etc/cinder/cinder.conf)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:49:26 + with message-id and subject line Bug#912991: fixed in cinder 2:13.0.1-1 has caused the Debian Bug report #912991, regarding cinder-common should configure my_ip directive in /etc/cinder/cinder.conf to be marked as done. This means that you

Bug#912987: marked as done (cinder-common is not filling value volume_group via debconf)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:49:26 + with message-id and subject line Bug#912987: fixed in cinder 2:13.0.1-1 has caused the Debian Bug report #912987, regarding cinder-common is not filling value volume_group via debconf to be marked as done. This means that you claim that the

Bug#912984: marked as done (cinder-common is not purging conf files from /etc/cinder)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:49:26 + with message-id and subject line Bug#912984: fixed in cinder 2:13.0.1-1 has caused the Debian Bug report #912984, regarding cinder-common is not purging conf files from /etc/cinder to be marked as done. This means that you claim that the problem

Bug#895765: marked as done (igv: FTBFS with java 9)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 15:34:25 + with message-id and subject line Bug#895765: fixed in igv 2.4.14+dfsg-2 has caused the Debian Bug report #895765, regarding igv: FTBFS with java 9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#913524: marked as done (python-xarray: failing autopkgtest with cftime 1.0.2)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 14:51:15 + with message-id and subject line Bug#913524: fixed in python-xarray 0.11.0-1 has caused the Debian Bug report #913524, regarding python-xarray: failing autopkgtest with cftime 1.0.2 to be marked as done. This means that you claim that the

Bug#906623: marked as done (heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory))

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 15:19:27 + with message-id and subject line Bug#906623: fixed in heimdal 7.5.0+dfsg-2.1 has caused the Debian Bug report #906623, regarding heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory) to be marked as done. This means that

Bug#912643: marked as done (biojava-live FTBFS with OpenJDK 11)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 15:49:23 + with message-id and subject line Bug#912643: fixed in biojava-live 1:1.7.1-8 has caused the Debian Bug report #912643, regarding biojava-live FTBFS with OpenJDK 11 to be marked as done. This means that you claim that the problem has been dealt

Bug#909429: marked as done (ITP: osmo-sgsn -- Serving GPRS Support Node for Mobile Networks)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:00:11 + with message-id and subject line Bug#909429: fixed in osmo-sgsn 1.3.0-1~exp1 has caused the Debian Bug report #909429, regarding ITP: osmo-sgsn -- Serving GPRS Support Node for Mobile Networks to be marked as done. This means that you claim that

Bug#909826: marked as done (ITP: theme-d - a Scheme-like language implementing static typing)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:00:12 + with message-id and subject line Bug#909826: fixed in theme-d 1.1.11-1 has caused the Debian Bug report #909826, regarding ITP: theme-d - a Scheme-like language implementing static typing to be marked as done. This means that you claim that the

Bug#904193: marked as done (ITP: osmo-bsc -- GSM Base Station Controller)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:00:10 + with message-id and subject line Bug#904193: fixed in osmo-bsc 1.2.1-1~exp1 has caused the Debian Bug report #904193, regarding ITP: osmo-bsc -- GSM Base Station Controller to be marked as done. This means that you claim that the problem has

Bug#913490: marked as done (coda: FTBFS (dh_auto_configure fails))

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 14:39:21 + with message-id and subject line Bug#913490: fixed in coda 2.19-1 has caused the Debian Bug report #913490, regarding coda: FTBFS (dh_auto_configure fails) to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913521: marked as done (python-xarray: Needs python3.6 for build tests but doesn't Build-Depend on it)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 14:51:15 + with message-id and subject line Bug#913521: fixed in python-xarray 0.11.0-1 has caused the Debian Bug report #913521, regarding python-xarray: Needs python3.6 for build tests but doesn't Build-Depend on it to be marked as done. This means that

Bug#910559: marked as done (cli-common-dev: dh_makeclilibs explicitly uses "chown", which means we cannot use Rules-Requires-Root: no)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 18:19:03 + with message-id and subject line Bug#910559: fixed in cli-common 0.9+nmu2 has caused the Debian Bug report #910559, regarding cli-common-dev: dh_makeclilibs explicitly uses "chown", which means we cannot use Rules-Requires-Root: no to be marked

Processed: closing 397675

2018-11-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 397675 1.6.3-1 Bug #397675 [ocfs2-tools] please do not check automatically ocfs2 filesystems Marked as fixed in versions ocfs2-tools/1.6.3-1. Bug #397675 [ocfs2-tools] please do not check automatically ocfs2 filesystems Marked Bug as done >

Bug#913407: marked as done (libsword-1.8.1: missing Breaks+Replaces: libsword11v5 (>= 1.8))

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:24:52 + with message-id and subject line Bug#913407: fixed in sword 1.8.1+dfsg-8 has caused the Debian Bug report #913407, regarding libsword-1.8.1: missing Breaks+Replaces: libsword11v5 (>= 1.8) to be marked as done. This means that you claim that the

Bug#913566: marked as done (htsjdk FTBFS with OpenJDK 11)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:22:14 + with message-id and subject line Bug#913566: fixed in htsjdk 2.16.1+dfsg-2 has caused the Debian Bug report #913566, regarding htsjdk FTBFS with OpenJDK 11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913511: marked as done (sword FTBFS with ICU 63.1)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:24:52 + with message-id and subject line Bug#913511: fixed in sword 1.8.1+dfsg-8 has caused the Debian Bug report #913511, regarding sword FTBFS with ICU 63.1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#912161: marked as done (sword: please make the build reproducible)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:24:52 + with message-id and subject line Bug#912161: fixed in sword 1.8.1+dfsg-8 has caused the Debian Bug report #912161, regarding sword: please make the build reproducible to be marked as done. This means that you claim that the problem has been

Bug#912971: marked as done (devscripts(1) manpage: broken SCRIPTS section)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#912971: fixed in devscripts 2.18.8 has caused the Debian Bug report #912971, regarding devscripts(1) manpage: broken SCRIPTS section to be marked as done. This means that you claim that the problem has been

Bug#913545: marked as done (outguess FTCBFS: uses the wrong compiler for jpeg-6b-steg)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 18:04:11 + with message-id and subject line Bug#913545: fixed in outguess 1:0.2.1-2 has caused the Debian Bug report #913545, regarding outguess FTCBFS: uses the wrong compiler for jpeg-6b-steg to be marked as done. This means that you claim that the

Bug#912403: marked as done (uscan: Regression for git mode)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#912403: fixed in devscripts 2.18.8 has caused the Debian Bug report #912403, regarding uscan: Regression for git mode to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#911969: marked as done (devscripts: more bad signal handling leading to insecure use of /tmp)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#911969: fixed in devscripts 2.18.8 has caused the Debian Bug report #911969, regarding devscripts: more bad signal handling leading to insecure use of /tmp to be marked as done. This means that you claim that

Bug#913008: marked as done (devscripts: Useless use of concatenation (.) or string in void context at /usr/share/perl5/Devscripts/Uscan/Downloader.pm line 106.)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#913008: fixed in devscripts 2.18.8 has caused the Debian Bug report #913008, regarding devscripts: Useless use of concatenation (.) or string in void context at /usr/share/perl5/Devscripts/Uscan/Downloader.pm

Bug#912083: marked as done (nmudiff: please support also neomutt)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#912083: fixed in devscripts 2.18.8 has caused the Debian Bug report #912083, regarding nmudiff: please support also neomutt to be marked as done. This means that you claim that the problem has been dealt

Bug#899073: marked as done ([uscan][RFC] please support something like uscan components for multiple tar.gz)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:19:14 + with message-id and subject line Bug#899073: fixed in devscripts 2.18.8 has caused the Debian Bug report #899073, regarding [uscan][RFC] please support something like uscan components for multiple tar.gz to be marked as done. This means that

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

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#766628: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #766628, regarding qpsmtpd: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the problem

Bug#780433: marked as done (qpsmtpd: French debconf templates translation)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#780433: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #780433, regarding qpsmtpd: French debconf templates translation to be marked as done. This means that you claim that the problem has been

Bug#815699: marked as done (qpsmtpd: [INTL:de] updated German debconf translation)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#815699: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #815699, regarding qpsmtpd: [INTL:de] updated German debconf translation to be marked as done. This means that you claim that the problem has

Bug#781340: marked as done ([INTL:da] Danish translation of the debconf templates qpsmtpd)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#781340: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #781340, regarding [INTL:da] Danish translation of the debconf templates qpsmtpd to be marked as done. This means that you claim that the

Processed: closing 911801

2018-11-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 911801 Bug #911801 [pcs] pacemaker: Cannot complete pcs cluster setup command, returns error HTTP401 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 911801:

Bug#859946: marked as done (qpsmtpd: [INTL:pt] Portuguese translation for debconf messages)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#859946: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #859946, regarding qpsmtpd: [INTL:pt] Portuguese translation for debconf messages to be marked as done. This means that you claim that the

Bug#872982: marked as done (qpsmtpd: [INTL:pt] Updated Portuguese translation for debconf messages)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#872982: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #872982, regarding qpsmtpd: [INTL:pt] Updated Portuguese translation for debconf messages to be marked as done. This means that you claim that

Bug#912044: marked as done (libterm-readline-ttytter-perl: FTBFS: Testsuite hangs)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:57:27 +0100 (CET) with message-id and subject line Re: pbuilder config has caused the Debian Bug report #912044, regarding libterm-readline-ttytter-perl: FTBFS: Testsuite hangs to be marked as done. This means that you claim that the problem has been dealt

Bug#819024: marked as done (qpsmtpd: [INTL:ja] Japanese debconf templates translation update)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:38:30 + with message-id and subject line Bug#819024: fixed in qpsmtpd 0.94-3 has caused the Debian Bug report #819024, regarding qpsmtpd: [INTL:ja] Japanese debconf templates translation update to be marked as done. This means that you claim that the

Bug#912392: marked as done (scilab: FTBFS with Java 11 due to javax.annotation removal)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:40:11 + with message-id and subject line Bug#912392: fixed in scilab 6.0.1-6 has caused the Debian Bug report #912392, regarding scilab: FTBFS with Java 11 due to javax.annotation removal to be marked as done. This means that you claim that the problem

Bug#881596: marked as done (evqueue-core: fails to install: rsyslog: unrecognized service)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#881596: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #881596, regarding evqueue-core: fails to install: rsyslog: unrecognized service to be marked as done. This means that you claim that the

Bug#883290: marked as done (evqueue-core: [INTL:ru] Russian translation of debconf template)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#883290: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #883290, regarding evqueue-core: [INTL:ru] Russian translation of debconf template to be marked as done. This means that you claim that the

Bug#883822: marked as done (evqueue-core: [INTL:de] German debconf translation)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#883822: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #883822, regarding evqueue-core: [INTL:de] German debconf translation to be marked as done. This means that you claim that the problem has

Bug#912862: marked as done (Please provide libgap.la)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:04:31 + with message-id and subject line Bug#912862: fixed in gap 4r10p0-1 has caused the Debian Bug report #912862, regarding Please provide libgap.la to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#882654: marked as done (evqueue-core: [INTL:nl] Dutch translation of debconf messages)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#882654: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #882654, regarding evqueue-core: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the

Bug#883302: marked as done (evqueue-core: [INTL:fr] French debconf translation)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#883302: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #883302, regarding evqueue-core: [INTL:fr] French debconf translation to be marked as done. This means that you claim that the problem has

Bug#884171: marked as done (evqueue-core: [INTL:pt] Portuguese translation for debconf messages)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:03:56 + with message-id and subject line Bug#884171: fixed in evqueue-core 2.1-1 has caused the Debian Bug report #884171, regarding evqueue-core: [INTL:pt] Portuguese translation for debconf messages to be marked as done. This means that you claim that

Bug#913577: marked as done (java-allocation-instrumenter FTBFS with ASM 7)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:05:17 + with message-id and subject line Bug#913577: fixed in java-allocation-instrumenter 3.1.0-2 has caused the Debian Bug report #913577, regarding java-allocation-instrumenter FTBFS with ASM 7 to be marked as done. This means that you claim that the

Bug#913578: marked as done (printer-driver-postscript-hp: PPDs are missing)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 20:35:57 + with message-id and subject line Bug#913578: fixed in hplip 3.18.10+dfsg0-3 has caused the Debian Bug report #913578, regarding printer-driver-postscript-hp: PPDs are missing to be marked as done. This means that you claim that the problem has

Bug#913518: marked as done (brisk-menu: successfully cross builds a broken package)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 20:35:43 + with message-id and subject line Bug#913518: fixed in brisk-menu 0.5.0-9 has caused the Debian Bug report #913518, regarding brisk-menu: successfully cross builds a broken package to be marked as done. This means that you claim that the problem

Bug#904810: marked as done (ITP: muttrc-mode-el -- Emacs major mode for editing muttrc)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:00:11 + with message-id and subject line Bug#904810: fixed in muttrc-mode-el 1.2+git20180915.aa1601a-1 has caused the Debian Bug report #904810, regarding ITP: muttrc-mode-el -- Emacs major mode for editing muttrc to be marked as done. This means that

Bug#913432: marked as done (thunar-media-tags-plugin: Build-Depends: libxml-parser-perl is cross-unsatisfiable)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 21:22:43 + with message-id and subject line Bug#913432: fixed in thunar-media-tags-plugin 0.3.0-2 has caused the Debian Bug report #913432, regarding thunar-media-tags-plugin: Build-Depends: libxml-parser-perl is cross-unsatisfiable to be marked as done.

Bug#913498: marked as done (qpsmtpd: [FTBFS] Does not build in unstable, prerequisite Time::TAI64 0 not found)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:24:50 +0100 with message-id and subject line qpsmtpd builds fine in unstable has caused the Debian Bug report #913498, regarding qpsmtpd: [FTBFS] Does not build in unstable, prerequisite Time::TAI64 0 not found to be marked as done. This means that you

Bug#913488: marked as done (scdaemon: gnupg --card-status does not recognize smart card via usb reader)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 16:23:53 -0500 with message-id <87y39yuh06@fifthhorseman.net> and subject line Re: [pkg-gnupg-maint] Bug#913488: scdaemon: gnupg --card-status does not recognize smart card via usb reader has caused the Debian Bug report #913488, regarding scdaemon: gnupg

Bug#913567: marked as done (python-numpy: Why depend on libatlas3-base?)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 12:06:44 -0500 with message-id and subject line Re: Bug#913567: python-numpy: Why depend on libatlas3-base? has caused the Debian Bug report #913567, regarding python-numpy: Why depend on libatlas3-base? to be marked as done. This means that you claim that

Bug#913459: marked as done (libvtk7.1-qt{,dev}: mipsel missing in the Architecture: lists)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 17:21:42 + with message-id and subject line Bug#913459: fixed in vtk7 7.1.1+dfsg1-9 has caused the Debian Bug report #913459, regarding libvtk7.1-qt{,dev}: mipsel missing in the Architecture: lists to be marked as done. This means that you claim that the

Bug#913570: marked as done (litecoin-qt: Hangs on start)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:19:22 + with message-id and subject line Bug#913570: fixed in litecoin 0.16.3-2 has caused the Debian Bug report #913570, regarding litecoin-qt: Hangs on start to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#909811: marked as done (RFS: muttrc-mode-el/1.2+git20180915.aa1601a-1 [ITP] [previously part of emacs-goodies-el])

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:24:40 + with message-id and subject line closing RFS: muttrc-mode-el/1.2+git20180915.aa1601a-1 [ITP] [previously part of emacs-goodies-el] has caused the Debian Bug report #909811, regarding RFS: muttrc-mode-el/1.2+git20180915.aa1601a-1 [ITP]

Bug#911553: marked as done (RFS: rtags/2.20-2 [ITP])

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:24:42 + with message-id and subject line closing RFS: rtags/2.20-2 [ITP] has caused the Debian Bug report #911553, regarding RFS: rtags/2.20-2 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#910604: marked as done (RFS: theme-d/1.1.11-1 [ITP])

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:24:39 + with message-id and subject line closing RFS: theme-d/1.1.11-1 [ITP] has caused the Debian Bug report #910604, regarding RFS: theme-d/1.1.11-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#909375: marked as done (nautilus: Trace/breakpoint trap)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:21 + with message-id and subject line Bug#908800: fixed in tracker 2.1.6-1 has caused the Debian Bug report #908800, regarding nautilus: Trace/breakpoint trap to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#912095: marked as done (missing dependency on tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:21 + with message-id and subject line Bug#908800: fixed in tracker 2.1.6-1 has caused the Debian Bug report #908800, regarding missing dependency on tracker to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#908800: marked as done (nautilus: can't use nautilus without tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:21 + with message-id and subject line Bug#908800: fixed in tracker 2.1.6-1 has caused the Debian Bug report #908800, regarding nautilus: can't use nautilus without tracker to be marked as done. This means that you claim that the problem has been

Bug#911999: marked as done (Undeclared dependency on tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:21 + with message-id and subject line Bug#908800: fixed in tracker 2.1.6-1 has caused the Debian Bug report #908800, regarding Undeclared dependency on tracker to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#913595: marked as done (CVE-2018-19120: kio-extras: HTML Thumbnailer automatic remote file access)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:02 + with message-id and subject line Bug#913595: fixed in kio-extras 4:18.08.3-1 has caused the Debian Bug report #913595, regarding CVE-2018-19120: kio-extras: HTML Thumbnailer automatic remote file access to be marked as done. This means that you

Bug#909375: marked as done (nautilus: Trace/breakpoint trap)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:30 + with message-id and subject line Bug#908800: fixed in tracker-miners 2.1.5-1 has caused the Debian Bug report #908800, regarding nautilus: Trace/breakpoint trap to be marked as done. This means that you claim that the problem has been dealt

Bug#912095: marked as done (missing dependency on tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:30 + with message-id and subject line Bug#908800: fixed in tracker-miners 2.1.5-1 has caused the Debian Bug report #908800, regarding missing dependency on tracker to be marked as done. This means that you claim that the problem has been dealt with.

Bug#911999: marked as done (Undeclared dependency on tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:30 + with message-id and subject line Bug#908800: fixed in tracker-miners 2.1.5-1 has caused the Debian Bug report #908800, regarding Undeclared dependency on tracker to be marked as done. This means that you claim that the problem has been dealt

Bug#908800: marked as done (nautilus: can't use nautilus without tracker)

2018-11-12 Thread Debian Bug Tracking System
Your message dated Mon, 12 Nov 2018 22:50:30 + with message-id and subject line Bug#908800: fixed in tracker-miners 2.1.5-1 has caused the Debian Bug report #908800, regarding nautilus: can't use nautilus without tracker to be marked as done. This means that you claim that the problem has