Bug#357665: marked as done (AppConfig::CGI.3pm.gz: mangled address)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 06:04:02 + with message-id and subject line Bug#357665: fixed in appconfig 1.71-2 has caused the Debian Bug report #357665, regarding AppConfig::CGI.3pm.gz: mangled address to be marked as done. This means that you claim that the problem has been dealt with

Bug#867578: marked as done (telegram-desktop: FTBFS with Qt 5.9: /usr/bin/ld: cannot find -lQt5PlatformSupport)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 3 Aug 2017 08:38:58 +0300 with message-id <68e84acd-4fc8-b28d-a8c9-028082a63...@ya.ru> and subject line Re: Bug#867578: telegram-desktop: FTBFS with Qt 5.9: /usr/bin/ld: cannot find -lQt5PlatformSupport has caused the Debian Bug report #867578, regarding telegram-desktop: F

Bug#870458: marked as done (nmu: pfstools_2.0.6-1)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 05:25:00 + with message-id <347fe199-c618-8cb9-0df1-be0fa61c8...@thykier.net> and subject line Re: Bug#870458: nmu: pfstools_2.0.6-1 has caused the Debian Bug report #870458, regarding nmu: pfstools_2.0.6-1 to be marked as done. This means that you claim tha

Bug#870402: marked as done (nmu: libvoikko_4.1-1)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 05:24:00 + with message-id <8431416f-2fe1-8af1-a829-1472c2e3d...@thykier.net> and subject line Re: Bug#870402: nmu: libvoikko_4.1-1 has caused the Debian Bug report #870402, regarding nmu: libvoikko_4.1-1 to be marked as done. This means that you claim that

Bug#864756: marked as done (Failover of VMs from dead nodes doesn't work with RBD or any other extstorage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 03:04:59 + with message-id and subject line Bug#864756: fixed in ganeti 2.15.2-10 has caused the Debian Bug report #864756, regarding Failover of VMs from dead nodes doesn't work with RBD or any other extstorage to be marked as done. This means that you cl

Bug#864754: marked as done (CPU affinity broken with Stretch (or backport python versions on Jessie))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 03:04:59 + with message-id and subject line Bug#864754: fixed in ganeti 2.15.2-10 has caused the Debian Bug report #864754, regarding CPU affinity broken with Stretch (or backport python versions on Jessie) to be marked as done. This means that you claim t

Bug#868601: marked as done (ganeti FTBFS: Can't find reST role named 'manpage': 'manpage')

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 03:04:59 + with message-id and subject line Bug#868601: fixed in ganeti 2.15.2-10 has caused the Debian Bug report #868601, regarding ganeti FTBFS: Can't find reST role named 'manpage': 'manpage' to be marked as done. This means that you claim that the prob

Bug#868606: marked as done (hol-light FTBFS: Error: This expression has type (MLast.loc * string Ploc.vala) Ploc.vala but an expression was expected of type MLast.loc * 'a)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 01:34:06 + with message-id and subject line Bug#868606: fixed in hol-light 20170109-2 has caused the Debian Bug report #868606, regarding hol-light FTBFS: Error: This expression has type (MLast.loc * string Ploc.vala) Ploc.vala but an expression was expecte

Bug#870490: marked as done (RFS: fizsh/1.0.9-1 (already in Debian))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 3 Aug 2017 02:38:37 +0200 with message-id <20170803003837.ooeu2vvo73fgw...@angband.pl> and subject line Re: Bug#870490: RFS: fizsh/1.0.9-1 (already in Debian) has caused the Debian Bug report #870490, regarding RFS: fizsh/1.0.9-1 (already in Debian) to be marked as done. Th

Bug#853680: marked as done (tgt: ftbfs with GCC-7)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 00:34:59 + with message-id and subject line Bug#853680: fixed in tgt 1:1.0.72-1 has caused the Debian Bug report #853680, regarding tgt: ftbfs with GCC-7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#861239: marked as done (Impossible to connect to SFTP servers)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2017 02:29:59 +0200 with message-id <1501720199.18425.1.ca...@debian.org> and subject line #861239 Impossible to connect to SFTP servers has caused the Debian Bug report #861239, regarding Impossible to connect to SFTP servers to be marked as done. This means that yo

Bug#870545: marked as done (libopenusb: hardcoded Pre-Depends on multiarch-support)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 22:05:08 + with message-id and subject line Bug#870545: fixed in libopenusb 1.1.11-2 has caused the Debian Bug report #870545, regarding libopenusb: hardcoded Pre-Depends on multiarch-support to be marked as done. This means that you claim that the problem

Bug#870558: marked as done (nas: hardcoded Pre-Depends on multiarch-support)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:53:52 + with message-id and subject line Bug#870558: fixed in nas 1.9.4-6 has caused the Debian Bug report #870558, regarding nas: hardcoded Pre-Depends on multiarch-support to be marked as done. This means that you claim that the problem has been dealt

Bug#870499: marked as done (wxmaxima: Plots too small)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:54:52 + with message-id and subject line Bug#870499: fixed in wxmaxima 16.12.2-3 has caused the Debian Bug report #870499, regarding wxmaxima: Plots too small to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#870516: marked as done (lzip FTCBFS: uses the build architecture compiler)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:52:15 + with message-id and subject line Bug#870516: fixed in lzip 1.19-3 has caused the Debian Bug report #870516, regarding lzip FTCBFS: uses the build architecture compiler to be marked as done. This means that you claim that the problem has been deal

Bug#797849: marked as done (lftp: Doesn't use ~/.config/lftp/rc as documented in man page)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 23:24:33 +0200 with message-id <1501709073.327.28.ca...@debian.org> and subject line Re: Bug#797849: lftp: Doesn't use ~/.config/lftp/rc as documented in man page has caused the Debian Bug report #797849, regarding lftp: Doesn't use ~/.config/lftp/rc as document

Bug#870510: marked as done (RFS: wxmaxima/16.12.2-3)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 23:29:28 +0200 with message-id <20170802212928.xtujd2kh567tp...@angband.pl> and subject line Re: Bug#870510: Subject: RFS: wxmaxima/16.12.2-3 has caused the Debian Bug report #870510, regarding RFS: wxmaxima/16.12.2-3 to be marked as done. This means that you cla

Processed: closing 839293

2017-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 839293 1.12-1 Bug #839293 [src:google-cloud-print-connector] google-cloud-print-connector: FTBFS - go install returned exit code 2 Marked as fixed in versions google-cloud-print-connector/1.12-1. Bug #839293 [src:google-cloud-print-connecto

Processed: closing 841590

2017-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 841590 1.12-1 Bug #841590 [src:google-cloud-print-connector] google-cloud-print-connector: FTBFS: # github.com/google/cups-connector/cups Marked as fixed in versions google-cloud-print-connector/1.12-1. Bug #841590 [src:google-cloud-print-c

Bug#870525: marked as done (Memory leaks in WriteMSLImage (upstream #636))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870525: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870525, regarding Memory leaks in WriteMSLImage (upstream #636) to be marked as done. This means that you claim that the problem

Bug#870527: marked as done (Memory-Leak in ReadPWPImage())

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870527: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870527, regarding Memory-Leak in ReadPWPImage() to be marked as done. This means that you claim that the problem has been dealt

Bug#870524: marked as done (memory leak in WriteMSLImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870524: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870524, regarding memory leak in WriteMSLImage to be marked as done. This means that you claim that the problem has been dealt w

Bug#870492: marked as done (memory leak in pdf coder)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870492: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870492, regarding memory leak in pdf coder to be marked as done. This means that you claim that the problem has been dealt with.

Bug#870502: marked as done (memory leak in ReadPICTImage #620)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870502: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870502, regarding memory leak in ReadPICTImage #620 to be marked as done. This means that you claim that the problem has been de

Bug#870478: marked as done (CVE-2017-11750)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870478: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870478, regarding CVE-2017-11750 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#870475: marked as done (memory leak in CALS coder)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870475: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870475, regarding memory leak in CALS coder to be marked as done. This means that you claim that the problem has been dealt with

Bug#870501: marked as done (memory leak in WritePICTImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870501: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870501, regarding memory leak in WritePICTImage to be marked as done. This means that you claim that the problem has been dealt

Bug#870504: marked as done (memory exhaustion in ReadSUNImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870504: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870504, regarding memory exhaustion in ReadSUNImage to be marked as done. This means that you claim that the problem has been de

Bug#870503: marked as done (memory leak in ReadSVGImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870503: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870503, regarding memory leak in ReadSVGImage to be marked as done. This means that you claim that the problem has been dealt wi

Bug#870530: marked as done (memory exhaustion in ReadPSDImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870530: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870530, regarding memory exhaustion in ReadPSDImage to be marked as done. This means that you claim that the problem has been de

Bug#870526: marked as done (avoid unbounded loop in pwp coder)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870526: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870526, regarding avoid unbounded loop in pwp coder to be marked as done. This means that you claim that the problem has been de

Bug#870489: marked as done (memory leak in WritePCXImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870489: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870489, regarding memory leak in WritePCXImage to be marked as done. This means that you claim that the problem has been dealt w

Bug#870483: marked as done (memory leak in WriteMAPImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870483: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870483, regarding memory leak in WriteMAPImage to be marked as done. This means that you claim that the problem has been dealt w

Bug#870481: marked as done (CVE-2017-11752)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870481: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870481, regarding CVE-2017-11752 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#870491: marked as done (memory exhaustion in ReadPCXImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870491: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870491, regarding memory exhaustion in ReadPCXImage to be marked as done. This means that you claim that the problem has been de

Bug#868967: marked as done (influxdb-python: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:41 + with message-id and subject line Bug#868967: fixed in influxdb-python 4.1.1-1 has caused the Debian Bug report #868967, regarding influxdb-python: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13 to be marked as

Bug#870482: marked as done (memory leak in WriteINLINEImage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:06:31 + with message-id and subject line Bug#870482: fixed in imagemagick 8:6.9.7.4+dfsg-16 has caused the Debian Bug report #870482, regarding memory leak in WriteINLINEImage to be marked as done. This means that you claim that the problem has been deal

Bug#870506: marked as done (dtksettings: FTBFS (32-bit): symbols not as expected)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 21:04:26 + with message-id and subject line Bug#870506: fixed in dtksettings 0.1.7-2 has caused the Debian Bug report #870506, regarding dtksettings: FTBFS (32-bit): symbols not as expected to be marked as done. This means that you claim that the problem ha

Bug#827973: marked as done (Please remove me from Uploaders)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 19:51:11 + with message-id and subject line Bug#827973: fixed in sage-extension 1.5.5-1 has caused the Debian Bug report #827973, regarding Please remove me from Uploaders to be marked as done. This means that you claim that the problem has been dealt with.

Bug#810854: marked as done (git-buildpackage: port to python3)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 19:34:05 + with message-id and subject line Bug#810854: fixed in git-buildpackage 0.9.0~exp0 has caused the Debian Bug report #810854, regarding git-buildpackage: port to python3 to be marked as done. This means that you claim that the problem has been deal

Bug#868854: marked as done (libfaad-dev: neaacdec.h contains PACKAGE_VERSION instead of the actual version)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 19:19:09 + with message-id and subject line Bug#868854: fixed in faad2 2.8.1-2 has caused the Debian Bug report #868854, regarding libfaad-dev: neaacdec.h contains PACKAGE_VERSION instead of the actual version to be marked as done. This means that you clai

Bug#868915: marked as done (gpac: FTBFS: faad_dec.c:408:35: error: expected ';' before 'PACKAGE_VERSION')

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 19:19:09 + with message-id and subject line Bug#868854: fixed in faad2 2.8.1-2 has caused the Debian Bug report #868854, regarding gpac: FTBFS: faad_dec.c:408:35: error: expected ';' before 'PACKAGE_VERSION' to be marked as done. This means that you claim

Bug#870484: marked as done (linux-image-4.9.0-3-amd64: nf_conntrack_ftp does not detect passive data connection as related)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 20:09:38 +0100 with message-id <1501700978.2701.43.ca...@decadent.org.uk> and subject line Re: Bug#870484: linux-image-4.9.0-3-amd64: nf_conntrack_ftp does not detect passive data connection as related has caused the Debian Bug report #870484, regarding linux-im

Bug#734709: marked as done (icedove: saved search virtual folder not initially listed in favourites on startup)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 14:51:50 -0400 with message-id <20170802185150.sozgjmtg3jr65...@x260.cruise.homelinux.net> and subject line Re: Bug#734709: icedove: saved search virtual folder not initially listed in favourites on startup has caused the Debian Bug report #734709, regarding iced

Bug#862321: marked as done (libdesktop-notify-perl: Please package 0.05 upstream release)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:49:37 + with message-id and subject line Bug#862321: fixed in libdesktop-notify-perl 0.05-1 has caused the Debian Bug report #862321, regarding libdesktop-notify-perl: Please package 0.05 upstream release to be marked as done. This means that you claim t

Bug#703036: marked as done (iceowl-extension: Prevent icedove to request creating of an email account on starting.)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 14:46:45 -0400 with message-id <20170802184645.4tirsoytsphpe...@x260.cruise.homelinux.net> and subject line Re: Bug#703036: iceowl-extension: Prevent icedove to request creating of an email account on starting. has caused the Debian Bug report #703036, regarding

Bug#783009: marked as done (mirror segfaults on huge destination directory)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 20:35:29 +0200 with message-id <1501698929.327.23.ca...@debian.org> and subject line Re: Bug#783009: mirror segfaults on huge destination directory has caused the Debian Bug report #783009, regarding mirror segfaults on huge destination directory to be marked as

Bug#786799: marked as done (lftp cant establish data connection when using ftpes)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 20:31:42 +0200 with message-id <1501698702.327.21.ca...@debian.org> and subject line Re: Bug#786799: lftp cant establish data connection when using ftpes has caused the Debian Bug report #786799, regarding lftp cant establish data connection when using ftpes to

Bug#850949: marked as done (icedove does not sync google calendars, claiming item.recurrenceInfo is null)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 14:37:15 -0400 with message-id <20170802183715.ebft4rtvsf7bz...@x260.cruise.homelinux.net> and subject line Re: Bug#850949: icedove does not sync google calendars, claiming item.recurrenceInfo is null has caused the Debian Bug report #850949, regarding icedove do

Bug#726163: marked as done (libsmbclient: excess dependencies?)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 20:18:50 +0200 with message-id and subject line Closing has caused the Debian Bug report #726163, regarding libsmbclient: excess dependencies? 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 no

Bug#827738: marked as done (fedmsg: Package unusable in sid (pkg_resources.DistributionNotFound: The 'Twisted_Core'))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #808654, regarding fedmsg: Package unusable in sid (pkg_resources.DistributionNotFound: The 'Twisted_Core') to be marked as done. This

Bug#868818: marked as done (RM: fedmsg -- RoQA; unmaintained, RC-buggy)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:40 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #868818, regarding RM: fedmsg -- RoQA; unmaintained, RC-buggy to be marked as done. This means that you claim that the problem has been

Bug#808654: marked as done (fedmsg: FTBFS offline: Download error on https://pypi.python.org/simple/Twisted_Core/)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #808654, regarding fedmsg: FTBFS offline: Download error on https://pypi.python.org/simple/Twisted_Core/ to be marked as done. This me

Bug#868508: marked as done (fedmsg: CVE-2017-1000001)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #868508, regarding fedmsg: CVE-2017-101 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#778419: marked as done (fedmsg: please make the build reproducible)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #778419, regarding fedmsg: please make the build reproducible to be marked as done. This means that you claim that the problem has been

Bug#842156: marked as done (fedmsg is broken and horribly out of date (0.9.3 < 0.17.2))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #842156, regarding fedmsg is broken and horribly out of date (0.9.3 < 0.17.2) to be marked as done. This means that you claim that the

Bug#855924: marked as done (fedmsg: FTBFS: Test failures)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 18:07:45 + with message-id and subject line Bug#868818: Removed package(s) from unstable has caused the Debian Bug report #855924, regarding fedmsg: FTBFS: Test failures to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#779737: marked as done (pptp-linux: VPN stoped working)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 18:34:09 +0200 with message-id <1501691...@msgid.manchmal.in-ulm.de> and subject line Closing has caused the Debian Bug report #779737, regarding pptp-linux: VPN stoped working to be marked as done. This means that you claim that the problem has been dealt with.

Bug#827974: marked as done (Please remove me from Uploaders)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 15:35:18 + with message-id and subject line Bug#827974: fixed in webdeveloper 1.2.13-1 has caused the Debian Bug report #827974, regarding Please remove me from Uploaders to be marked as done. This means that you claim that the problem has been dealt with.

Bug#870440: marked as done (libc++abi-dev: typo in Breaks)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 15:05:16 + with message-id and subject line Bug#870440: fixed in libc++ 3.9.1-3 has caused the Debian Bug report #870440, regarding libc++abi-dev: typo in Breaks to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#846924: marked as done ([arping] New upstream release available / debian/watch fails)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 15:04:06 + with message-id and subject line Bug#846924: fixed in arping 2.19-1 has caused the Debian Bug report #846924, regarding [arping] New upstream release available / debian/watch fails to be marked as done. This means that you claim that the problem

Bug#865500: marked as done (ITP: node-libs-browser -- The node core libs for in browser usage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 15:00:09 + with message-id and subject line Bug#865500: fixed in node-libs-browser 2.0.0-1 has caused the Debian Bug report #865500, regarding ITP: node-libs-browser -- The node core libs for in browser usage to be marked as done. This means that you claim

Bug#806242: marked as done (ITP: node-libs-browser -- node core libs for in browser usage)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 15:00:09 + with message-id and subject line Bug#865500: fixed in node-libs-browser 2.0.0-1 has caused the Debian Bug report #865500, regarding ITP: node-libs-browser -- node core libs for in browser usage to be marked as done. This means that you claim that

Bug#869181: marked as done (librospack-dev: Incorrect libtinyxml dependency)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 13:49:20 + with message-id and subject line Bug#869181: fixed in ros-rospack 2.4.1-2 has caused the Debian Bug report #869181, regarding librospack-dev: Incorrect libtinyxml dependency to be marked as done. This means that you claim that the problem has bee

Processed: closing 389928

2017-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 389928 Bug #389928 [arping] arping: suggested extra options Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 389928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=389928 Debian Bug Trac

Bug#836004: marked as done (python-gflags: please make the build reproducible)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 13:21:02 + with message-id and subject line Bug#836004: fixed in python-gflags 1.5.1-3 has caused the Debian Bug report #836004, regarding python-gflags: please make the build reproducible to be marked as done. This means that you claim that the problem has

Bug#843101: marked as done (python-hiredis: please make the build reproducible)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 13:07:09 + with message-id and subject line Bug#843101: fixed in python-hiredis 0.2.0-2 has caused the Debian Bug report #843101, regarding python-hiredis: please make the build reproducible to be marked as done. This means that you claim that the problem h

Bug#793500: marked as done (libhtmlparser-java: /​usr/​share/​doc/​libhtmlparser-​java-​doc/​api/​ is not always included in the built package)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 14:45:02 +0200 with message-id <1895f581-31bb-6886-eb6c-a3662e400...@gmail.com> and subject line Re: libhtmlparser-java: /​usr/​share/​doc/​libhtmlparser-​java-​doc/​api/​ is not always included in the built package has caused the Debian Bug report #793500, rega

Bug#869747: marked as done (liborcania-dev: undefined strnstr reference on non-Linux)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 12:20:15 + with message-id and subject line Bug#869747: fixed in orcania 1.1-3 has caused the Debian Bug report #869747, regarding liborcania-dev: undefined strnstr reference on non-Linux to be marked as done. This means that you claim that the problem has

Bug#867697: marked as done (ldapscripts: please update to 2.0.8)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 14:36:31 +0300 with message-id <20170802143631.55813...@brick.gerasiov.net> and subject line Fw: ldapscripts_2.0.8-1_source.changes ACCEPTED into unstable has caused the Debian Bug report #867697, regarding ldapscripts: please update to 2.0.8 to be marked as done.

Bug#867607: marked as done (botch: change in file layout in libjs-jquery-tablesorter requires adaptation)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:34:38 + with message-id and subject line Bug#867607: fixed in botch 0.21-4 has caused the Debian Bug report #867607, regarding botch: change in file layout in libjs-jquery-tablesorter requires adaptation to be marked as done. This means that you claim t

Bug#867005: marked as done (botch FTBFS: E722 do not use bare except')

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:34:38 + with message-id and subject line Bug#867005: fixed in botch 0.21-4 has caused the Debian Bug report #867005, regarding botch FTBFS: E722 do not use bare except' to be marked as done. This means that you claim that the problem has been dealt with.

Bug#869852: marked as done (Please build-depend on ocamlbuild)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:34:38 + with message-id and subject line Bug#869852: fixed in botch 0.21-4 has caused the Debian Bug report #869852, regarding Please build-depend on ocamlbuild to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: closing 782380

2017-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 782380 Bug #782380 [src:mailman-api] mailman-api: please make the build reproducible Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 782380: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#868494: marked as done (ITP: dtksettings -- Deepin Tool Kit Settings library)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:00:10 + with message-id and subject line Bug#868494: fixed in dtksettings 0.1.7-1 has caused the Debian Bug report #868494, regarding ITP: dtksettings -- Deepin Tool Kit Settings library to be marked as done. This means that you claim that the problem ha

Bug#780187: marked as done (ITP: python-coloredlogs -- Colored stream handler for the Python logging module)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:00:11 + with message-id and subject line Bug#780187: fixed in python-coloredlogs 7.1-1 has caused the Debian Bug report #780187, regarding ITP: python-coloredlogs -- Colored stream handler for the Python logging module to be marked as done. This means t

Bug#828940: marked as done (ITP: python-dropbox -- Official Dropbox API Client)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 11:00:12 + with message-id and subject line Bug#828940: fixed in python-dropbox 8.0.0-1 has caused the Debian Bug report #828940, regarding ITP: python-dropbox -- Official Dropbox API Client to be marked as done. This means that you claim that the problem h

Bug#820809: marked as done (wsdl4j: please make the build reproducible (environment))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 12:53:20 +0200 with message-id <0b02cb85-2fbe-2b7c-78c7-5bcb0d834...@gmail.com> and subject line Re: Bug#820809: wsdl4j: please make the build reproducible (environment) has caused the Debian Bug report #820809, regarding wsdl4j: please make the build reproducibl

Bug#868622: marked as done (mathgl FTBFS: error: 'op_lshift' is not a member of 'octave_value')

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 10:21:10 + with message-id and subject line Bug#868622: fixed in mathgl 2.4.1-2 has caused the Debian Bug report #868622, regarding mathgl FTBFS: error: 'op_lshift' is not a member of 'octave_value' to be marked as done. This means that you claim that the p

Bug#820086: marked as done (antlr3: v3.5 breaks existing grammars)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 11:41:27 +0200 with message-id <2872bfd9-43a7-a240-f6cd-e163f3b5c...@gmail.com> and subject line Re: antlr3: v3.5 breaks existing grammars has caused the Debian Bug report #820086, regarding antlr3: v3.5 breaks existing grammars to be marked as done. This means t

Bug#869871: marked as done (exim4-config: /etc/mailname is ignored)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 11:19:12 +0200 with message-id <20170802091912.sowieompqlzmc...@argenau.bebt.de> and subject line Re: Bug#869871: exim4-config: /etc/mailname is ignored has caused the Debian Bug report #869871, regarding exim4-config: /etc/mailname is ignored to be marked as done

Processed: forcemerge

2017-08-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 870410 src:ruby-truncato Bug #870410 [ruby-truncato] gitlab: fails to install: could not find compatible versions for gem "nokogiri" Bug reassigned from package 'ruby-truncato' to 'src:ruby-truncato'. Ignoring request to alter found vers

Bug#492461: marked as done (please remove the if-up.d script)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 08:49:07 + with message-id and subject line Bug#492461: fixed in arping 2.14-2 has caused the Debian Bug report #492461, regarding please remove the if-up.d script to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#866831: marked as done (ITA: arping -- sends IP and/or ARP pings (to the MAC address))

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 08:49:07 + with message-id and subject line Bug#866831: fixed in arping 2.14-2 has caused the Debian Bug report #866831, regarding ITA: arping -- sends IP and/or ARP pings (to the MAC address) to be marked as done. This means that you claim that the problem

Bug#870444: marked as done (libglvnd: FTBFS on arm64: no _glapi_tls_Current@Base)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:19:13 + with message-id and subject line Bug#870444: fixed in libglvnd 0.2.999+git20170802-1 has caused the Debian Bug report #870444, regarding libglvnd: FTBFS on arm64: no _glapi_tls_Current@Base to be marked as done. This means that you claim that the

Bug#108504: marked as done (LEGO USB Tower Support)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 2 Aug 2017 09:16:44 +0200 with message-id <20170802071644.ga15...@diskless.uio.no> and subject line Re: LEGO USB Tower Support has caused the Debian Bug report #108504, regarding LEGO USB Tower Support to be marked as done. This means that you claim that the problem has bee

Bug#866536: marked as done (jpy FTBFS on mips/mipsel: 1 Python unit test(s) failed. Installation is likely broken.)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:05:17 + with message-id and subject line Bug#866536: fixed in jpy 0.8-8 has caused the Debian Bug report #866536, regarding jpy FTBFS on mips/mipsel: 1 Python unit test(s) failed. Installation is likely broken. to be marked as done. This means that you

Bug#867685: marked as done (Drop gpgv1.4-udeb)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:05:05 + with message-id and subject line Bug#867685: fixed in gnupg1 1.4.22-1 has caused the Debian Bug report #867685, regarding Drop gpgv1.4-udeb to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

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

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:05:05 + with message-id and subject line Bug#845695: fixed in gnupg1 1.4.22-1 has caused the Debian Bug report #845695, regarding gnupg1: [INTL:nl] Dutch po file for the gnupg1 package to be marked as done. This means that you claim that the problem has

Bug#760354: marked as done (gnupg: --faked-system-time option documented, but not understood)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:05:05 + with message-id and subject line Bug#760354: fixed in gnupg1 1.4.22-1 has caused the Debian Bug report #760354, regarding gnupg: --faked-system-time option documented, but not understood to be marked as done. This means that you claim that the pr

Bug#867917: marked as done (chromium-browser: Build-Depends on deprecated libgnome-keyring-dev)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:00:12 + with message-id and subject line Bug#867917: fixed in chromium-browser 60.0.3112.72-1 has caused the Debian Bug report #867917, regarding chromium-browser: Build-Depends on deprecated libgnome-keyring-dev to be marked as done. This means that you

Bug#868926: marked as done (chromium-browser: FTBFS: ../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:47:29: error: variable 'gfx::{anonymous}::PrimeSyncStart(int)::local_dma_buf_sync sync_start' has

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:00:12 + with message-id and subject line Bug#868926: fixed in chromium-browser 60.0.3112.72-1 has caused the Debian Bug report #868926, regarding chromium-browser: FTBFS: ../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:47:29: error: variable 'gfx::{an

Bug#864565: marked as done (chromium-shell: Couldn't mmap v8 natives data file, status code is 1)

2017-08-02 Thread Debian Bug Tracking System
Your message dated Wed, 02 Aug 2017 07:00:12 + with message-id and subject line Bug#864565: fixed in chromium-browser 60.0.3112.72-1 has caused the Debian Bug report #864565, regarding chromium-shell: Couldn't mmap v8 natives data file, status code is 1 to be marked as done. This means that y