Bug#729951: ITP: requests-aws -- AWS authentication for Amazon S3 for the wonderful python-requests module.

2013-11-19 Thread Thomas Bechtold
Package: wnpp Severity: wishlist Owner: Thomas Bechtold * Package name: requests-aws Version : 0.1.4 Upstream Author : Paul Tax * URL : https://pypi.python.org/pypi/requests-aws/0.1.4 * License : BSD Programming Lang: Python Description : AWS authentic

Bug#729959: ITP: libmm-qt -- Qt wrapper for ModemManager DBus API

2013-11-19 Thread Maximiliano Curia
Package: wnpp Severity: wishlist Owner: Maximiliano Curia * Package name: libmm-qt Version : 0.5.1 Upstream Author : Will Stephenson , Lamarque Souza , Daniel Nicoletti * URL : https://projects.kde.org/projects/extragear/libs/li

Bug#729971: ITP: libnm-qt -- Qt wrapper for NetworkManager API

2013-11-19 Thread Maximiliano Curia
Package: wnpp Severity: wishlist Owner: Maximiliano Curia * Package name: libnm-qt Version : 0.9.0.1 Upstream Author : Ilia Kats , Daniel Nicoletti , Jan Grulich , Lamarque Souza , Will Stephenson * U

Re: Bug#729660: ITP: xemacs21 -- highly customizable text editor

2013-11-19 Thread Henrique de Moraes Holschuh
On Sun, 17 Nov 2013, Russ Allbery wrote: > Sune Vuorela writes: > > On 2013-11-16, Russ Allbery wrote: > >> If someone proposed to remove nvi from the archive because vim is > >> better, I would be quite annoyed. If it ever did get removed from the > >> archive, I would probably adopt it and rei

Re: Bug#729660: ITP: xemacs21 -- highly customizable text editor

2013-11-19 Thread Russ Allbery
Henrique de Moraes Holschuh writes: > On Sun, 17 Nov 2013, Russ Allbery wrote: >> Yeah, I know, which is part of why I used it for an example. I looked >> at it yesterday and will probably adopt it at some point when I have >> enough free time to do a proper job on the initial upload. > File an

Re: Bug#729660: ITP: xemacs21 -- highly customizable text editor

2013-11-19 Thread Henrique de Moraes Holschuh
On Tue, 19 Nov 2013, Russ Allbery wrote: > Henrique de Moraes Holschuh writes: > > On Sun, 17 Nov 2013, Russ Allbery wrote: > > >> Yeah, I know, which is part of why I used it for an example. I looked > >> at it yesterday and will probably adopt it at some point when I have > >> enough free time