Bug#858860: RFS: arpwatch [ITA]

2017-04-09 Thread Lukas Schwaighofer
Hi Hugo, On Wed, 5 Apr 2017 18:25:04 +0200 Hugo Lefeuvre wrote: > Are you already a member of the team ? If yes, could you move your git > repository to > https://anonscm.debian.org/git/pkg-security/arpwatch.git ? I've now officially joined the team, the repository is available at that URL. I'

Bug#840750: RFS: picocoin/0.1-2.gbp43047g

2017-04-09 Thread Joel DeJesus
Thank you for the reply/update. I have uploaded a new source package to fix some of the smaller issues with the control files, copyrights, etc. However, I seem to be stuck at what to do with the library name, libccoin. I was planning on just have libccoin as the package name and just managing th

Trigger to activate bash-completion

2017-04-09 Thread Eriberto Mota
Hi, I am trying implement completion in dcfldd. I already have a debian/dcfldd.bash-completion and a debian/rules with 'dh $@ --with bash-completion'. My current problem is I need to execute 'exec bash' to completion work. Is there a trigger to activate completion after the package install? Any p

Re: Trigger to activate bash-completion

2017-04-09 Thread Paul Wise
On Mon, Apr 10, 2017 at 10:09 AM, Eriberto Mota wrote: > My current problem is I need to execute 'exec bash' to completion > work. Is there a trigger to activate completion after the package > install? Any postinst action? Packages don't get to interfere with user processes, so no you cannot do t

Bug#840750: RFS: picocoin/0.1-2.gbp43047g

2017-04-09 Thread David Steele
On Sun, Apr 9, 2017 at 9:13 PM, Joel DeJesus wrote: > I have uploaded a new source package to fix some of the smaller issues > with the control files, copyrights, etc. However, I seem to be stuck at > what to do with the library name, libccoin. > > I was planning on just have libccoin as the pack

Bug#859988: RFS: gcc-6-doc/6.3.0-1

2017-04-09 Thread 郭溢譞
Package: sponsorship-requests Severity: normal Control: block 859974 by -1 Dear mentors, I'm looking for a sponsor for my package gcc-6-doc. Changes for this upload: gcc-6-doc (6.3.0-1) unstable; urgency=medium . * New upstream release. * Synced patches with gcc-6, 6.3.0-12. * Build m

Bug#859988: marked as done (RFS: gcc-6-doc/6.3.0-1)

2017-04-09 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 07:23:45 +0200 with message-id <20170410052345.dp3tnj47u2dtr...@angband.pl> and subject line Re: Bug#859988: RFS: gcc-6-doc/6.3.0-1 has caused the Debian Bug report #859988, regarding RFS: gcc-6-doc/6.3.0-1 to be marked as done. This means that you claim that th

Bug#859988: RFS: gcc-6-doc/6.3.0-1

2017-04-09 Thread Adam Borowski
On Sun, Apr 09, 2017 at 11:44:03PM -0400, Guo Yixuan wrote: > I'm looking for a sponsor for my package gcc-6-doc. > * Package name: gcc-6-doc > Version : 6.3.0-1 Not sure if this package can be autobuilt; if it won't before the evening, I'll do that manually. -- ⢀⣴⠾⠻⢶⣦⠀ Meow! ⣾⠁⢠⠒

Bug#859073: RFS: groonga/7.0.1-1

2017-04-09 Thread Kentaro Hayashi
On Sun, 9 Apr 2017 02:18:07 +0200 Adam Borowski wrote: > > This is a complex package that's going to be a part of Stretch; it's really > not the time for a new major upstream version. > > Thus, wouldn't you want to upload to experimental, and/or make a targetted > fix for the kfreebsd FTBFS? W