Bug#804520: ITP: astroscrappy -- Optimized Cosmic Ray Annihilation in Python

2015-11-08 Thread Ole Streicher
Package: wnpp Owner: Ole Streicher Severity: wishlist X-Debbugs-Cc: debian-devel@lists.debian.org,debian-as...@lists.debian.org,debian-pyt...@lists.debian.org * Package name: astroscrappy Version : 1.0.3 Upstream Author : Curtis McCully * URL : https://github.com/astr

Bug#804517: ITP: golang-github-rackspace-gophercloud -- Go SDK for OpenStack.

2015-11-08 Thread Potter, Tim (Converged Cloud)
X-Debbugs-CC: debian-devel@lists.debian.org, pkg-go-maintain...@lists.alioth.debian.org Package: wnpp Severity: wishlist Owner: Tim Potter * Package name: golang-github-rackspace-gophercloud Version : 0.0.0+git20151102.687.d471e57-1 Upstream Author : Rackspace, Inc. * URL

Re: [HEADSUP] dropping xconsole support from default rsyslog configuration

2015-11-08 Thread Marco d'Itri
On Nov 08, Michael Biebl wrote: > What I'm not quite sure yet is, if I should add a NEWS entry for that. I > guess for most users it would just be useless noise during the upgrade > process. But I'm willing to add it if others think it's useful to have. Please don't. Having xconsole enabled by de

Re: #791857 ITP: daemonize -- tool to run a command as a daemon

2015-11-08 Thread Dmitry Smirnov
On Thu, 09 Jul 2015 15:23:55 +0200 Martín Ferrari wrote: > > Does this have any advantage over start-stop-daemon? > > I can say that it does: start-stop-daemon misses some functionality you > need for programs that don't daemonise and log to stdout/stderr, which > is something I needed only last we

[HEADSUP] dropping xconsole support from default rsyslog configuration

2015-11-08 Thread Michael Biebl
Hi, when first packaging the rsyslog package for Debian back in 2007, I based the default configuration in /etc/rsyslog.conf on what was shipped in sysklogds /etc/syslog.conf back at the time. This includes the following rule: # The named pipe /dev/xconsole is for the `xconsole' utility. To us

Re: (newbie) Disruptive LIRC package update.

2015-11-08 Thread Alexandre Detiste
Le dimanche 8 novembre 2015, 19:28:38 Dominique Dumont a écrit : > > If I rephrase, with the current setup, 'service lirc start' starts 4 daemon > processes. > > Which means the user only has to type one command to start and stop all of > them. > > With the new setup. the user will have to deal

Re: (newbie) Disruptive LIRC package update.

2015-11-08 Thread Dominique Dumont
On Sunday 08 November 2015 15:19:30 Alec Leamas wrote: > Some tooling to build the new configuration from the old will indeed be > required. This is actually some work - it includes a complete lircd > command line parser with ~18 options. Bit it's certainly doable. Good to know > The real reason

Bug#804453: RFP: xul-ext-toggle-word-wrap -- Icedove extension to toggle word wrapping from menu

2015-11-08 Thread Balint Reczey
Package: wnpp Severity: wishlist * Package name: xul-ext-toggle-word-wrap Version : 1.9.1 * URL : https://addons.mozilla.org/en-US/thunderbird/addon/toggle-word-wrap/ * License : MPL 1.1/GPL 2.0/LGPL 2.1 Programming Lang: JavaScript Description : Toggle w

Bug#804448: RFP: ruby-os -- gem for easy telling if you’re on windows or not

2015-11-08 Thread Axel Beckert
Package: wnpp Severity: wishlist Control: block 658863 by -1 * Package name: ruby-os Version : 0.9.6 Upstream Author : Roger Pack * URL or Web page : https://github.com/rdp/os * License : MIT Description : easy telling if you’re on windows or not. The OS gem allow

Bug#804439: ITP: saws -- A Supercharged AWS Command Line Interface

2015-11-08 Thread Dariusz Dwornikowski
Package: wnpp Severity: wishlist Owner: Dariusz Dwornikowski * Package name: saws Version : 0.3.2 Upstream Author : Martin Donne * URL : https://github.com/donnemartin/saws * License : Apache 2.0 Programming Lang: Python Description : A Supercharged AW

Re: (newbie) Disruptive LIRC package update.

2015-11-08 Thread Alec Leamas
On 07/11/15 10:05, Dominique Dumont wrote: > On Friday 06 November 2015 18:48:29 Alec Leamas wrote: >> So, an upgrade will not support hardware.conf. Which basically breaks >> each and every installation. While we could (i. e., should) provide docs >> and perhaps some tooling to ease the process,