Bug#919257: RFS: antlr4-cpp-runtime/4.7.2-1 [ITP] -- ANTLR Parser Generator - C++ runtime support

2019-01-13 Thread Andrius Merkys
Package: sponsorship-requests Severity: normal Control: block 918109 by -1 Dear mentors, I am looking for a sponsor for my package "antlr4-cpp-runtime". Package is required to update mysql-workbench (#902798). * Package name: antlr4-cpp-runtime Version : 4.7.2-1 Upstream

Bug#919097: marked as done (RFS: bitz-server/2.0.3-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 04:20:17 + with message-id and subject line closing RFS: bitz-server/2.0.3-1 has caused the Debian Bug report #919097, regarding RFS: bitz-server/2.0.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#915718: marked as done (RFS: arno-iptables-firewall/2.0.3-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 23:52:59 + with message-id and subject line has caused the Debian Bug report #915718, regarding RFS: arno-iptables-firewall/2.0.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#919127: RFS: kio-gdrive/1.2.5+fixedtarball-1

2019-01-13 Thread Nicholas D Steeves
On Sun, Jan 13, 2019 at 12:02:30PM +0200, Adrian Bunk wrote: > On Sat, Jan 12, 2019 at 03:05:55PM -0700, Nicholas D Steeves wrote: > >... > > Changes since the last upload: > > > > kio-gdrive (1.2.5+fixedtarball-1) unstable; urgency=medium > > > > * Restore missing translations. (Closes:

Bug#918957: marked as done (RFS: ifmetric/0.3-5)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Jan 2019 00:15:03 +0100 with message-id <20190113231503.uvs25jymkswxq...@angband.pl> and subject line Re: Bug#918957: RFS: ifmetric/0.3-5 has caused the Debian Bug report #918957, regarding RFS: ifmetric/0.3-5 to be marked as done. This means that you claim that the

Bug#919016: marked as done (RFS: tintin++/2.01.5-1 [ITA])

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 23:43:55 +0100 with message-id <20190113224355.ehlqtat3q4ekt...@angband.pl> and subject line Re: Bug#919016: RFS: tintin++/2.01.5-1 [ITA] has caused the Debian Bug report #919016, regarding RFS: tintin++/2.01.5-1 [ITA] to be marked as done. This means that you

Bug#918911: marked as done (RFS: duperemove/0.11.1-3)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 23:22:52 +0100 with message-id <2019011352.v6h6qtho6wlrq...@angband.pl> and subject line Re: Bug#918911: RFS: duperemove/0.11.1-3 has caused the Debian Bug report #918911, regarding RFS: duperemove/0.11.1-3 to be marked as done. This means that you claim

Bug#918450: marked as done (RFS: elpy/1.28.0-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 22:20:06 + with message-id and subject line closing RFS: elpy/1.28.0-1 has caused the Debian Bug report #918450, regarding RFS: elpy/1.28.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#918450: RFS: elpy/1.28.0-1

2019-01-13 Thread Nicholas D Steeves
Hi Chris, On Sun, Jan 13, 2019 at 06:26:31PM +, Chris Lamb wrote: > Nicholas D Steeves wrote: > > > elpy (1.28.0-1) unstable; urgency=medium > > … uploaded. Thank you :-) > Regarding: > > ifneq ($(filter nodoc,$(DEB_BUILD_PROFILES)),) > echo -e "\nnodoc profile enabled,

Bug#918450: RFS: elpy/1.28.0-1

2019-01-13 Thread Chris Lamb
Nicholas D Steeves wrote: > elpy (1.28.0-1) unstable; urgency=medium … uploaded. Regarding: ifneq ($(filter nodoc,$(DEB_BUILD_PROFILES)),) echo -e "\nnodoc profile enabled, building without sphinxdoc..\n" dh $@ --with elpa,python3 --buildsystem=pybuild else

Bug#907295: marked as done (RFS: scrcpy/1.3-1 [ITP])

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 17:09:00 + with message-id and subject line closing RFS: scrcpy/1.3-1 [ITP] has caused the Debian Bug report #907295, regarding RFS: scrcpy/1.3-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#919175: marked as done (RFS: nautilus-admin/1.1.9-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 11:14:14 -0500 with message-id and subject line Re: RFS: nautilus-admin/1.1.9-1 has caused the Debian Bug report #919175, regarding RFS: nautilus-admin/1.1.9-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#919131: marked as done (RFS: apt-listbugs/0.1.27)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 16:39:44 +0100 with message-id <20190113163944.3609b484b7bb973ebf25c...@paranoici.org> and subject line Re: RFS: apt-listbugs/0.1.27 has caused the Debian Bug report #919131, regarding RFS: apt-listbugs/0.1.27 to be marked as done. This means that you claim

Bug#919175: RFS: nautilus-admin/1.1.9-1

2019-01-13 Thread Carlos Maddela
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "nautilus-admin" * Package name: nautilus-admin Version : 1.1.9-1 Upstream Author : Bruno Nova * URL : https://github.com/brunonova/nautilus-admin *

Bug#919127: marked as done (RFS: kio-gdrive/1.2.5+fixedtarball-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 12:02:30 +0200 with message-id <20190113100230.GA20563@localhost> and subject line Re: Bug#919127: RFS: kio-gdrive/1.2.5+fixedtarball-1 has caused the Debian Bug report #919127, regarding RFS: kio-gdrive/1.2.5+fixedtarball-1 to be marked as done. This means

Bug#919105: marked as done (RFS: uriparser/0.9.1-1)

2019-01-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Jan 2019 11:53:57 +0200 with message-id <20190113095357.GA15481@localhost> and subject line Re: Bug#919105: RFS: uriparser/0.9.1-1 has caused the Debian Bug report #919105, regarding RFS: uriparser/0.9.1-1 to be marked as done. This means that you claim that the problem