Bug#827149: marked as done (RFS: triggerhappy/0.4.0-1)

Your message dated Tue, 14 Jun 2016 04:28:13 + with message-id <e1bcfxv-0005ia...@quantz.debian.org> and subject line closing RFS: triggerhappy/0.4.0-1 has caused the Debian Bug report #827149, regarding RFS: triggerhappy/0.4.0-1 to be marked as done. This means that you

Bug#827149: RFS: triggerhappy/0.4.0-1

control: owner -1 andre...@debian.org (no idea why I was replying from a wrong email) On 13 June 2016 at 16:03, Gianfranco Costamagna wrote: > control: owner -1 andrew.shado...@gmail.com > >>I think I could. > setting you as owner :) Thanks! >>There's

Bug#827149: RFS: triggerhappy/0.4.0-1

control: owner -1 andrew.shado...@gmail.com >I think I could. setting you as owner :) >There's https://github.com/wertarbyte/triggerhappy/commits/systemd but >I haven't looked how much does it conflict with the master branch. I did merge the systemd branch into master, and it merged

Bug#827149: RFS: triggerhappy/0.4.0-1

On 13 June 2016 at 15:47, Gianfranco Costamagna wrote: > control: owner -1 ! > >>Hi, could you please also ship my systemd integration (see upstream PR and >>branch)? > > > Andrew, do you plan to upload the package once this is fixed? I think I could. > I see Jakub

Bug#827149: RFS: triggerhappy/0.4.0-1

control: owner -1 ! >Hi, could you please also ship my systemd integration (see upstream PR and >branch)? Andrew, do you plan to upload the package once this is fixed? I see Jakub already did a wonderful review, and the current package on mentors seems to address his concerns. I see your

Bug#827149: RFS: triggerhappy/0.4.0-1

On 13 Jun 2016 00:03, "Stefan Tomanek" wrote: > > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "triggerhappy" > > * Package name: triggerhappy >Version : 0.4.0-1 >

Bug#827149: RFS: triggerhappy/0.4.0-1

Control: tags -1 + moreinfo [I don't intend to sponsor this package.] * Stefan Tomanek , 2016-06-12, 23:59: https://mentors.debian.net/debian/pool/main/t/triggerhappy/triggerhappy_0.4.0-1.dsc Bumping compat to 9 is not documented in the changelog. Please

Bug#827149: RFS: triggerhappy/0.4.0-1

Good morning, Dies schrieb Sean Whitton (spwhit...@spwhitton.name): > On Sun, Jun 12, 2016 at 11:59:34PM +0200, Stefan Tomanek wrote: > > Changes since the last upload: > > > >* update to version 0.4.0 (closes: bug#827079, bug#769184) > > Although this bug closing syntax is acceptable,

Bug#827149: RFS: triggerhappy/0.4.0-1

Dear Stegan, On Sun, Jun 12, 2016 at 11:59:34PM +0200, Stefan Tomanek wrote: > Changes since the last upload: > >* update to version 0.4.0 (closes: bug#827079, bug#769184) Although this bug closing syntax is acceptable, it's marked as "not preferred" Developer's Reference section 5.8.4.

Bug#827149: RFS: triggerhappy/0.4.0-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "triggerhappy" * Package name: triggerhappy Version : 0.4.0-1 Upstream Author : Stefan Tomanek * URL :

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.4-2 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : https://github.com/wertarbyte/triggerhappy * License : GPLv3 Section

Re: RFS: triggerhappy (retry)

On Wed, Mar 09, 2011 at 02:57:12PM +0100, Stefan Tomanek wrote: Dear mentors, I am looking for a sponsor for my package triggerhappy. [skipped] Dear Stefan, Thanks for your work on this software. I am not a DD, and cannot be an uploader for your package, but I have a strong opinion that

Re: RFS: triggerhappy (retry)

Hello and thanks for your reply, Dies schrieb Stanislav Maslovski (stanislav.maslov...@gmail.com): But the orig.tar.gz does not have it either, so it is probably OK by now, however, you may consider adding it in future, because your work may be of interest to other distributions, and for them

RFS: triggerhappy (retry)

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.4-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : https://github.com/wertarbyte/triggerhappy * License : GPLv3 Section

RFS: triggerhappy (retry)

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.3-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : https://github.com/wertarbyte/triggerhappy * License : GPLv3 Section

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.3-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : https://github.com/wertarbyte/triggerhappy * License : GPLv3 Section

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.2-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy * License : GPL Section

Re: RFS: triggerhappy

Dies schrieb Nick Leverton (n...@leverton.org): Every .c-file has to contain that header? Sure, possible, but seems very awkward? It helps, the Debian tool licensecheck can then scan and report on the contents of the package. Also if a source is borrowed elsewhere, the authorship is

Re: RFS: triggerhappy

On Sat, Dec 18, 2010 at 03:10:21PM +0100, Stefan Tomanek wrote: Looking for a way of globally assigning hotkey handlers to the special keys found on my notebooks, I developed triggerhappy. I also use it to control headless systems, e.g. a ARM based MPD jukebox which is controlled by a USB

Re: RFS: triggerhappy

Dies schrieb Nick Leverton (n...@leverton.org): I gather that this is a new package to Debian. Your debian/changelog should probably start from new in that case. You could perhaps move the existing debian/changelog to changelog.OLD or similar, if you want to retain the history of the code's

Re: RFS: triggerhappy

On Fri, Dec 24, 2010 at 06:00:53PM +0100, Stefan Tomanek wrote: Dies schrieb Nick Leverton (n...@leverton.org): I gather that this is a new package to Debian. Your debian/changelog should probably start from new in that case. I'm not sure about that and I heard different opinions about

Re: RFS: triggerhappy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-20 21:20, Stefan Tomanek wrote: Dies schrieb Niels Thykier (ni...@thykier.net): Checking cmdsocket.c... [cmdsocket.c:126]: (error) Resource leak: fd [...] Okay, perhaps you could document this in the code that this is intentional

Re: RFS: triggerhappy

Dies schrieb Niels Thykier (ni...@thykier.net): It might be because you have a different version than I; I am using 1.44 (from testing). So am I: ste...@exa:~$ cppcheck --version Cppcheck 1.44 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of

Re: RFS: triggerhappy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-21 11:48, Stefan Tomanek wrote: Dies schrieb Niels Thykier (ni...@thykier.net): It might be because you have a different version than I; I am using 1.44 (from testing). So am I: ste...@exa:~$ cppcheck --version Cppcheck 1.44

Re: RFS: triggerhappy

Dies schrieb Niels Thykier (ni...@thykier.net): I just cloned the git repository and I cannot reproduce any more either. I suspect this is because you fixed the buffer variable going out of scope. Strange, I did not touch anything in that section of code. But anyhow, I'm glad that warning is

Re: RFS: triggerhappy

Dies schrieb Niels Thykier (ni...@thykier.net): I just cloned the git repository and I cannot reproduce any more either. I suspect this is because you fixed the buffer variable going out of scope. OK, I think now I incorporated all your suggested fixes and uploaded a new package with version

Re: RFS: triggerhappy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-18 15:10, Stefan Tomanek wrote: Dear mentors, [...] Looking for a way of globally assigning hotkey handlers to the special keys found on my notebooks, I developed triggerhappy. I also use it to control headless systems, e.g. a

Re: RFS: triggerhappy

Dies schrieb Niels Thykier (ni...@thykier.net): Though the upstream code might need a little attention (or some clarification); e.g. cppcheck finds a resource leak: Checking cmdsocket.c... [cmdsocket.c:126]: (error) Resource leak: fd Looking at the code I am not sure what the intention

Re: RFS: triggerhappy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2010-12-20 17:08, Stefan Tomanek wrote: Dies schrieb Niels Thykier (ni...@thykier.net): Though the upstream code might need a little attention (or some clarification); e.g. cppcheck finds a resource leak: Checking cmdsocket.c...

Re: RFS: triggerhappy

Dies schrieb Niels Thykier (ni...@thykier.net): Checking cmdsocket.c... [cmdsocket.c:126]: (error) Resource leak: fd [...] Okay, perhaps you could document this in the code that this is intentional (e.g. transmitting the fd and the leak is a false-positive)? I'm playing around with

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.3.1-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy * License : GPL Section

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

On Fri, Dec 10, 2010 at 11:43:17AM +0100, Stefan Tomanek wrote: Dies schrieb Stanislav Maslovski (stanislav.maslov...@gmail.com): Just a note for completeness: although not properly documented, acpid reacts to quite a few non-acpi events, including volume control buttons and cd-related

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Dies schrieb Stanislav Maslovski (stanislav.maslov...@gmail.com): Just a note for completeness: although not properly documented, acpid reacts to quite a few non-acpi events, including volume control buttons and cd-related buttons found on many laptops (as of ver. 2.0.7). It didn't use to to

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): Would it be easy and would it be sensible to teach esekeyd these features? Triggerhappy 0.3.0 brings some new features; individual devices can now be tagged, so that pressing a certain key on a USB keyboard can trigger a hotkey handler, while

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

On Mon, Nov 29, 2010 at 01:14:21AM +0100, Stefan Tomanek wrote: Dies schrieb Jonathan Nieder (jrnie...@gmail.com): This information could be useful for both package descriptions. (Maybe, for triggerhappy: That is, this is similar to esekeyd but it also supports such and such,

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): This information could be useful for both package descriptions. (Maybe, for triggerhappy: That is, this is similar to esekeyd but it also supports such and such, allowing you to such and such. and for esekeyd: This

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): This information could be useful for both package descriptions. (Maybe, for triggerhappy: That is, this is similar to esekeyd but it also supports such and such, allowing you to such and such. and for esekeyd: This

Re: RFS: triggerhappy

Stefan Tomanek wrote: Dies schrieb Jonathan Nieder (jrnie...@gmail.com): How does this compare to Rick van Rein's funkey[1]? Hm, funkey does require a kernel patch und looks quite dated? Funky Daemon which demonstrates how to parse the /dev/funkey character device. Thanks for a quick

Re: RFS: triggerhappy

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): How does triggerhappy compare to Krzysztof Burghardt's esekeyd? I think esekeyd can only handle KEY events, while triggerhappy can also process Switch and button events. I am also unsure whether esekeyd support the hotplugging of input devices

esekeyd and triggerhappy (Re: RFS: triggerhappy)

Hi Krzysztof and Stefan, Stefan Tomanek wrote: I think esekeyd can only handle KEY events, while triggerhappy can also process Switch and button events. I am also unsure whether esekeyd support the hotplugging of input devices (done in triggerhappy by a udev script) or daemon control via

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): I think esekeyd can only handle KEY events, while triggerhappy can also process Switch and button events. I am also unsure whether esekeyd support the hotplugging of input devices (done in triggerhappy by a udev script) or daemon

Re: esekeyd and triggerhappy (Re: RFS: triggerhappy)

Stefan Tomanek wrote: I think merging the two programs would be difficult. Although young, triggerhappy has accumulated quite a few features that would require a redesigning many aspects of esekeyd (multiple devices, command socket, multiple config files). This information could be useful

Re: RFS: triggerhappy [fixed mistake in URL]

Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): I understand :) But now that you're packaging it, you should let people know by retitling the bug to ITP and setting yourself as the bug owner (otherwise someone else might start working on it too, only to discover the work has already been

Re: RFS: triggerhappy [fixed mistake in URL]

Stefan Tomanek wrote: Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): I understand :) But now that you're packaging it, you should let people know by retitling the bug to ITP and setting yourself as the bug owner (otherwise someone else might start working on it too, only to discover

Re: RFS: triggerhappy [fixed mistake in URL]

Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): As a matter of fact, I do :) You retitled it to the exact same title it already has: Indeed, I just noticed. Classic case of copypaste gone wrong. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of

Re: RFS: triggerhappy

Hi Stefan, Stefan Tomanek wrote: * URL : https://github.com/wertarbyte/triggerhappy [...] My motivation for maintaining this package is: I've written this small program to fill a need not covered by any existing program, so I think having it in Debian and making it available to

Re: RFS: triggerhappy

Dies schrieb Jonathan Nieder (jrnie...@gmail.com): How does this compare to Rick van Rein's funkey[1]? Hm, funkey does require a kernel patch und looks quite dated? Funky Daemon which demonstrates how to parse the /dev/funkey character device. As I said, triggerhappy uses the

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.6-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy/ * License : GPL Section

RFS: triggerhappy [fixed mistake in URL]

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.6-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy/ * License : GPL Section

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.6-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy/ * License : GPL Section

Re: RFS: triggerhappy [fixed mistake in URL]

Hi Stefan, Stefan Tomanek wrote: I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.6-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy/ * License

Re: RFS: triggerhappy [fixed mistake in URL]

Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): I see you've now opened a bug for your package (#603842), but you still need to close it in your changelog. And it should be an ITP bug owned by you, not an RFP. I opened that bug before I uploaded the package here, hoping that someone else

Re: RFS: triggerhappy [fixed mistake in URL]

Stefan Tomanek wrote: Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): I see you've now opened a bug for your package (#603842), but you still need to close it in your changelog. And it should be an ITP bug owned by you, not an RFP. I opened that bug before I uploaded the package

Re: RFS: triggerhappy

On Wed, Nov 17, 2010 at 11:49:06PM +0100, Stefan Tomanek wrote: Dear mentors, Hi Stefan I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.3-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL

RFS: triggerhappy

Dear mentors, I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.3-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy * License : GPL Section

Re: RFS: triggerhappy

Hi Stefan, Stefan Tomanek wrote: I am looking for a sponsor for my package triggerhappy. * Package name: triggerhappy Version : 0.1.3-1 Upstream Author : Stefan Tomanek stefan.tomanek...@wertarbyte.de * URL : http://github.com/wertarbyte/triggerhappy * License

Re: RFS: triggerhappy

Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): lintian -I --pedantic actually gives a few warnings: I: triggerhappy source: debian-watch-file-is-missing W: triggerhappy: description-starts-with-leading-spaces I: triggerhappy: init.d-script-does-not-provide-itself

Re: RFS: triggerhappy

Dies schrieb Benoît Knecht (benoit.kne...@fsfe.org): lintian -I --pedantic actually gives a few warnings: I: triggerhappy source: debian-watch-file-is-missing W: triggerhappy: description-starts-with-leading-spaces I: triggerhappy: init.d-script-does-not-provide-itself