Bug#817120: ITP: python-pylxd -- Python library for interacting with LXD REST API

2016-03-08 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-pylxd
  Version : 2.0.0~b1
  Upstream Author : Canonical Ltd
* URL : https://github.com/lxd/pylxd
* License : Apache-2.0
  Programming Lang: Python
  Description : Python library for interacting with LXD REST API

 LXD offers a REST API to remotely manage containers over the network, using an
 image based workflow and with support for live migration.
 .
 pylxd is a small Python library for interacting the with the LXD REST API.

Note from maintainer: this is a new dependency for Manila, the file share as a
service of OpenStack. I am currently unsure if I will maintain LXD itself in
Debian, this is currently an ongoing discussion.



Re: debian-www / debian-doc teams no longer responsive [Was: Re: Bad release in install documentation]

2016-03-08 Thread Rhonda D'Vine
* Holger Wansing  [2016-03-07 10:33:15 CET]:
> Laura Arjona Reina  wrote:
> > I'm in debwww since some days ago and this is one of the things I wanted to 
> > look at, but couldn't put time yet.
> > I hope I can have a look at it in the following days.
> > 
> 
> That would be fine indeed.
> 
> While I think about, if recruting new people to the team wouldn't make
> sense, nevertheless. As said above, debian-www and debian-doc seem not 
> very responsive ATM ...

 Personally I wouldn't object to adding you to the team from what I've
seen from you so far.  You would need to go through NM process
(non-uploading maybe) for that though because it doesn't make much sense
to add people to debwww on alioth but actually not being able to deploy
the changes in the end.  Also adding non DDs to the alioth project would
require an additional level of checking what got added by a non DD of
the group before deploying anything while it is a bit more convenient
(and trust based) so far with respect to expecting that only people are
able to push there who are also able to deploy it directly.

 So long,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los  |
Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los|



Upgrading xrdp

2016-03-08 Thread Andreas Tille
Hi Vincent,

since I need an up to date xrdp at work I upgraded the packaging in
collab-maint to the latest upstream version.  Considering the package is
in collab-maint I guess it is OK for you that I added myself to
Uploaders.  It would be nice if you could check my changes whether you
are happy with these.  If I do not hear from you I'll upload in three
days the current status in Git[1].

Meanwhile I'll point upstream to the available patches in Debian.

Kind regards

  Andreas.

[1] https://anonscm.debian.org/cgit/collab-maint/xrdp.git

-- 
http://fam-tille.de



Re: Upgrading xrdp

2016-03-08 Thread Vincent Bernat
 ❦  8 mars 2016 15:03 +0100, Andreas Tille  :

> since I need an up to date xrdp at work I upgraded the packaging in
> collab-maint to the latest upstream version.  Considering the package is
> in collab-maint I guess it is OK for you that I added myself to
> Uploaders.  It would be nice if you could check my changes whether you
> are happy with these.  If I do not hear from you I'll upload in three
> days the current status in Git[1].

Yes, no problem. The package is up to adoption but there is already an
ITA. See #719624. However, I didn't get more news since January. But I
didn't try to reach out.
-- 
Use the fundamental control flow constructs.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Re: How to deal with "assets" packages shadowing real upstream

2016-03-08 Thread Jonathan Dowland
On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
> I personally feel it is a bug to not track the true upstream of a 
> project, but that seems not part of our Policy.  Should I respect fellow 
> package maintainers prioritizing convenience over elegance, or insist 
> that we should strive towards perfection?

The former. "Perfection is the enemy of good" (or "shipped")



Bug#817156: ITP: singular3 -- Computer Algebra System for Polynomial Computations (version 3)

2016-03-08 Thread Ximin Luo
Package: wnpp
Severity: wishlist
Owner: Ximin Luo 

* Package name: singular3
  Version : 3.1.7
  Upstream Author : Singular Team 
* URL : https://www.singular.uni-kl.de/
* License : GPL
  Programming Lang: C++
  Description : Computer Algebra System for Polynomial Computations 
(version 3)

SINGULAR is a Computer Algebra System (CAS) for polynomial computations with
emphasis on the special needs of commutative algebra, algebraic geometry,
and singularity theory.

The latest version, 4, is already in Debian. However, we need version 3 as a
dependency package of Sagemath; the two versions have incompatible APIs and 
ABIs.



Re: Upgrading xrdp

2016-03-08 Thread Andreas Tille
Hi Vincent,

thanks fro the quick response.

On Tue, Mar 08, 2016 at 03:07:51PM +0100, Vincent Bernat wrote:
>  ❦  8 mars 2016 15:03 +0100, Andreas Tille  :
> 
> > since I need an up to date xrdp at work I upgraded the packaging in
> > collab-maint to the latest upstream version.  Considering the package is
> > in collab-maint I guess it is OK for you that I added myself to
> > Uploaders.  It would be nice if you could check my changes whether you
> > are happy with these.  If I do not hear from you I'll upload in three
> > days the current status in Git[1].
> 
> Yes, no problem. The package is up to adoption but there is already an
> ITA. See #719624. However, I didn't get more news since January. But I
> didn't try to reach out.

If anybody of the people responding tp the ITA bug like to become the
main maintainer of the package I'd be more than happy to sponsor the
package.  As far as the situation is now I'll upload my current work in
Git tomorrow.

Kind regards

   Andreas.

-- 
http://fam-tille.de



Re: Bug#719624: Upgrading xrdp

2016-03-08 Thread Dominik George
Hi,

>> Yes, no problem. The package is up to adoption but there is already
>an
>> ITA. See #719624. However, I didn't get more news since January. But
>I
>> didn't try to reach out.
>
>If anybody of the people responding tp the ITA bug like to become the
>main maintainer of the package I'd be more than happy to sponsor the
>package.  As far as the situation is now I'll upload my current work in
>Git tomorrow.

The current version is here because the package is being adopted by the Debian 
Edu team:

https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=debian-edu/pkg-team/xrdp.git;a=summary

The package is pending upload to experimental.

If you have anything special about your packaging, feel free to share it so we 
can incorporate it.

Cheers,
Nik
-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-151-61623918

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)



Bug#817173: ITP: libplack-middleware-logwarn-perl -- converts warnings to log messages

2016-03-08 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: libplack-middleware-logwarn-perl
  Version : 0.001002
  Upstream Author : Geoffrey Darling 
* URL : https://metacpan.org/pod/Plack::Middleware::LogWarn
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : converts warnings to log messages

 Plack::Middleware::LogWarn is a Plack::Middleware component that will
 help you get warnings into a logger. You probably want to use some sort
 of real logging system such as Log::Log4perl and another
 Plack::Middleware such as Plack::Middleware::Log4perl.
 .
 Plack is a set of tools similar to Ruby's Rack or Python's Paste for
 WSGI. It implements the Perl Server Gateway Interface (PSGI) standard
 interface, which allows developers to decouple their web application
 framework from the local web server environment.

This package will be maintained in the Debian Perl team.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3w9tAAoJECx8MUbBoAEhM/YQAIHt4BGe6WfHCi8x7dRcgllv
RURwhJW8hvHiQORxCTxJJJIuCBN8QnaDm5z2XH15zNaGNlI2p8VWP2CVVDsSsXDQ
AJn15AVdEembIJOSN+dZFHUtkrTJCcMGQilAOejh6xK6QJl9OiIoO27SB5Mrg5jW
5D3oB/QsSMC/jQTULthB3gONJnA3Zex+y0sa227p1/cCCPKoD20sUJ86G5XwYAyw
3zsun1FdVcZbucwObYHqLU8SL4ulVGv8+n5EyfvNIBBbV3lLl213zLYLbcF19o5v
n0gBdfnClabxVW5H7thh/VTivbEJtaYgL/r2v79FJtEa5QjVkNdQ0BGz0Me6QCvr
LElV6M8vJx0mQpSY/CuSI8TY/xwy+WCBPjukB2Ys9krtkPo6oUF4RmDU8g9801+0
/WjM99HRhoyln5yMmbMBXLAZ3xVb7O/9vBoOPGm5d8wbMB04Gc17JOFIAOxRt6vM
r86Wyg6jwz04GKQn/qCHBaHok0jlo0Sfo82Fp/cYnK/RZt37CmunluUbetPFBZ8h
iwVXsmVQZAG09HiUJOdR61+P3b5+5GLteI5SgMAEGhFb/+pugozmDuP6E27KQ+8W
ESYOENi6pYwKkymy1mhkQc9KT4/FNx8YEBKAzD02PMCZMvvIPAjNnTY77/UHYNke
t/4mjKgujXpIqVAa6XEQ
=a5SR
-END PGP SIGNATURE-



Re: Bug#719624: Upgrading xrdp

2016-03-08 Thread Andreas Tille
[Setting reply-to Debian-Edu]

On Tue, Mar 08, 2016 at 06:29:12PM +0100, Dominik George wrote:
> >If anybody of the people responding tp the ITA bug like to become the
> >main maintainer of the package I'd be more than happy to sponsor the
> >package.  As far as the situation is now I'll upload my current work in
> >Git tomorrow.
> 
> The current version is here because the package is being adopted by the 
> Debian Edu team:
> 
> https://alioth.debian.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=debian-edu/pkg-team/xrdp.git;a=summary
> 
> The package is pending upload to experimental.
> 
> If you have anything special about your packaging, feel free to share it so 
> we can incorporate it.

Is there any point in droping the history from debian/changelog and
feeding it with non-Debian releases instead?  I'm perfectly happy with
moving the package to Debian Edu. However, I have some concerns:

  0. The fact that the development of the package happened silently
 and in parallel to an existing Debian package.

  1. There is no defined way to get the upstream source - there is just
  # We don’t provide a get-orig-source target because submodules
 in debian/rules.
 I would really prefer the gbp layout featuring an upstream and a
 pristine-tar branch

  2. You should *definitely* restore the old changelog of xrdp and
 assemble all changes between the current released package (0.6.1-2)
 to your release candidate.

  3. Why do you plan
  a) a non-official (random?) Git commit rather than a release?
  b) uploading to experimental rather than unstable?

Kind regards

   Andreas.

-- 
http://fam-tille.de



Re: Bug#719624: Upgrading xrdp

2016-03-08 Thread Dominik George
Hi,

most of your concerns are being addressed already (restoring history and such). 
Please do not make it more difficult, an experienced DD (Mike Gabriel) is 
working with us.

>  3. Why do you plan
>  a) a non-official (random?) Git commit rather than a release?

Because there is no current release. Upstream does not make releases anymore. 
The picked commit is not random. It is verified to work and includes a lot of 
stuff we negotiated with upstream (license issues, patches from Debian, etc.). 
It's the best we could get, and it works.

>  b) uploading to experimental rather than unstable?

Because the package is a major change (e.g. switching from x11vnc to x11rdp by 
default).

-nik
-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296

Dominik George · Mobil: +49-151-61623918

Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Contributor

LPIC-3 Linux Enterprise Professional (Security)



Bug#817175: ITP: how2 -- stackoverflow from the terminal

2016-03-08 Thread Ondřej Nový
Package: wnpp
Severity: wishlist
Owner: "Ondřej Nový" 

* Package name: how2
  Version : 1.1.0
  Upstream Author : Claudio Santini 
* URL : https://github.com/santinic/how2/
* License : MIT
  Programming Lang: Javascript/Node.JS
  Description : stackoverflow from the terminal

Simple CLI/TUI for searching in Stackoverflow questions database.

I'm DM so I need sponsor for first upload.



Re: How to deal with "assets" packages shadowing real upstream

2016-03-08 Thread Bas Wijnen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Mar 07, 2016 at 03:12:10PM +0100, Jonas Smedegaard wrote:
> Oh - I just discovered that this _is_ covered by Policy §4.13 already.

Reading that again, I see that it says code copies are acceptable if the code
is meant to be used that way (with GNU autotools as an example in the
footnote).  For convenience, I quoted the whole thing below.

I think consensus has changed on this issue: this practically means "run
configure as shipped by upstream".  As far as I know, we now recommend
regenerating everything from source (configure.ac, Makefile.am).  Should this
be changed in policy?

Thanks,
Bas



4.13 Convenience copies of code

Some software packages include in their distribution convenience copies of code
from other software packages, generally so that users compiling from source
don't have to download multiple packages. Debian packages should not make use
of these convenience copies unless the included package is explicitly intended
to be used in this way.[29] If the included code is already in the Debian
archive in the form of a library, the Debian packaging should ensure that
binary packages reference the libraries already in Debian and the convenience
copy is not used. If the included code is not already in Debian, it should be
packaged separately as a prerequisite if possible. [30] 

[29] For example, parts of the GNU build system work like this.
[30] Having multiple copies of the same code in Debian is inefficient, often
 creates either static linking or shared library conflicts, and, most
 importantly, increases the difficulty of handling security vulnerabilities
 in the duplicated code.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3xiUAAoJEJzRfVgHwHE6WOgP/0D9QUq1YIA35swoccr+NHTF
NR3/JPc2CHhml0g8R90QPKRFnn+bBOtVC+660R9y5dCWinF1+dgSi1PRXwgVN/yi
iMAJyWlOKhu0p5otlWhWL5ikEBQNlNwL4p2+o/mJwTlkmCzXqjiv5oTbcS5ZMsWE
4+GyQNJS77UrIQ5pznBIf5pWcnVElECXp/Ayd1/dW1zr+nftHR1f/4feyd/z2yLv
F+Qyo1RQd2ig8WM++fvXbvjfjMHj56OUNGkZb+9aiKXVXgsaKjVS98jKOZ8140iM
JLjqZEZn3Uw73NozgoAN42OKQQa46G/3XjSsSiiXN/rnRl2DdS8K/Z1tG+QX0z/P
IB8Rs+/FEqg22Az9hmtJ+QhPrgEovv+CMQu0ZTy8Va6ah0n7cAE21fPKMuL/1VW1
izx5kFEQLpiU70po/xmlKpMXPZ4HnwuSZWL8wp2t5ofI2knZC5x52pkJ2kKNxvy1
Agv4S9RviKzf9F4VkvnjSEumX5EQs6vJ6QwvgYGVGVCgwcvfRVa1PotcULDktesb
oik7ZH8E0YQPh3mYYttmnjswuPRZ9YQUpS55bTUv9hi2gnR3+7eBdCL18cOQgFx2
Ta6R4/gPO67sSOTGoIptIPELcquNPpZ2XNSqXmxrDQMjS3/82N2yF7FASZ6Hhe+G
vqNNj9w1JIZ1r/157ROZ
=Ynrt
-END PGP SIGNATURE-



Re: How to deal with "assets" packages shadowing real upstream

2016-03-08 Thread Bas Wijnen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Mar 08, 2016 at 02:14:10PM +, Jonathan Dowland wrote:
> On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
> > I personally feel it is a bug to not track the true upstream of a 
> > project, but that seems not part of our Policy.  Should I respect fellow 
> > package maintainers prioritizing convenience over elegance, or insist 
> > that we should strive towards perfection?
> 
> The former. "Perfection is the enemy of good" (or "shipped")

No, both.  We should respect each other's choices in what we do and don't work
on, but if something is wrong it deserves a bug report.  Bug reports aren't
commands to go fix things; they are helpful notifications that something is in
need of fixing.

Thanks,
Bas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW3xk6AAoJEJzRfVgHwHE6khYP/3oXfN2CmcsPpxbeeuZDCrgq
Ycj4JBfzTxOIYrWFBSxbFCOoMlcSqmuhRrc4Tim9GYn1GBl7ljC1so2BfVSGs2Ei
Cg5nREyO8xz5pZ+LZb2+6r94Nf/8PUpFGyYbdbRkyK1rCtiAeSMkGQh1vb6NRdn/
Q8HQ4wzhewMV1+qoEuwLbwuv3KngsGXsSDrETG9UxgOkMlK9EowvZJ5WRV08jJ5w
LROQ9rW0OXtK6Ql+uQgGoS41gTpEmyfhjh3P+CS1+wgvKUzzkP1t3/h/fLNgEREQ
+9wzDd1ggvoCtKbOw77FErY34V/uOEDyrMPlAQI0kRW1dOTeCMMXwy2iEy4oloE6
yHIyhUCSQhCDJoQi6BLeLY76GhIuK9wQG+ZOQyBsiga+0u7gB0h2jQKyGfxu5jCL
zQQLnkY/u6m+/wOEk3ugxNmBQNMJdYkq0me7SW1Tg5zk/jR0KcCUywOQLTnZ+lFO
6h6+KlBFHkmpawZkYcF85V7WodUVuIY/5oowtiz3Vh9zcFlf7QKso0QoqQ2vIVGD
5ENMH1zeMtiBmXcmfz5YJDyU1l/eY/2DaH+9ouJlk6xiYNw+CHWZIikQzO16tITr
3BD4mQUc7t+v71cb+I1NM/WTn7SCAANu4LBnsIHA5Sl1qE0IWA//eOzo7BuiOr0/
eftUsMzjpr95Ix0lOW01
=mpkU
-END PGP SIGNATURE-



Bug#817197: ITP: vhostmd -- Virtualisation host metrics daemon

2016-03-08 Thread Michael-John Turner
Package: wnpp
Severity: wishlist
Owner: Michael-John Turner 

* Package name: vhostmd
  Version : 0.4
  Upstream Author : Jim Fehlig 
* URL : https://gitorious.org/vhostmd/vhostmd/
* License : GPL
  Programming Lang: C
  Description : Virtualisation host metrics daemon

Daemon vhostmd provides a "metrics communication channel" between a host
and its hosted virtual machines, allowing limited introspection of host
resource usage from within virtual machines.

vhostmd is useful for virtualisation hosts to monitor metrics within
guests - it supports both KVM and Xen. The daemon is available as
standard in RHEL and SUSE, amongst others.

I'm a former DD (mj@d.o) looking to reapply for DD status so would need a
sponsor.



Re: How to deal with "assets" packages shadowing real upstream

2016-03-08 Thread Jonas Smedegaard
Quoting Bas Wijnen (2016-03-08 19:23:18)
> On Mon, Mar 07, 2016 at 03:12:10PM +0100, Jonas Smedegaard wrote:
>> Oh - I just discovered that this _is_ covered by Policy §4.13 
>> already.
>
> Reading that again, I see that it says code copies are acceptable if 
> the code is meant to be used that way (with GNU autotools as an 
> example in the footnote).  For convenience, I quoted the whole thing 
> below.
>
> I think consensus has changed on this issue: this practically means 
> "run configure as shipped by upstream".  As far as I know, we now 
> recommend regenerating everything from source (configure.ac, 
> Makefile.am).  Should this be changed in policy?

I do not interpret it like that.

I interpret it as "redistribute upstream source as-is when it includes 
code copies of autotools, because that code is meant to be included with 
all projects using it".  I do not read into it that Policy dictates 
whether to then trust those pieces of code, nor (as some do) to skip 
documenting copyright and licensing for those files.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


Bug#817200: RFA: yt -- Framework for analyzing and visualizing simulation data

2016-03-08 Thread Kacper Kowalik

Package: wnpp
X-Debbugs-CC: debian-as...@lists.debian.org, debian-devel@lists.debian.org

As per my mail to yt-dev mailing list:

http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/2016-March/019977.html

I no longer have resources to keep maintaining this package. I hope new 
maintainer will step up soon.


Cheers,
Kacper



Bug#817203: ITP: libplack-middleware-logany-perl -- use Log::Any to handle logging from your Plack app

2016-03-08 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

* Package name: libplack-middleware-logany-perl
  Version : 0.001
  Upstream Author : Michael Alan Dorman 
* URL : https://metacpan.org/pod/Plack::Middleware::LogAny
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : use Log::Any to handle logging from your Plack app

 Plack::Middleware::LogAny  is a Plack::Middleware component that allows
 you to use Log::Any to handle the logging object, psgix.logger.
 .
 It really tries to be the thinnest possible shim, so it doesn't handle
 any configuration beyond setting the category to which messages from
 plack might be logged.
 .
 Plack is a set of tools similar to Ruby's Rack or Python's Paste for
 WSGI. It implements the Perl Server Gateway Interface (PSGI) standard
 interface, which allows developers to decouple their web application
 framework from the local web server environment.

The package will be maintained in the Debian Perl team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJW32BuAAoJECx8MUbBoAEh/s8P/Aw5aKMCHRulTSt2ut7M1HVn
PKV9n/8MuFFKvgxqLpY9E58vNycW1CrHUNdSlexdeOW4RzE66u64HM73xSbQyxvB
L8XJ/QnDOVPnocBUWjAVTbDAHuNp8ADQ8XYGclZY++N6NYpaWtjsXX6IdOqJdL7B
nRWakrmGdC0QYmgmF9epIGgXvUZ5lKzviX3iOtTpRIRiiP5MwUlaSg4UkI1EZQaM
I+U745FedNMMbeDoU/w0PmDQS/C/rXdPmBBdlutXOipNfbprRRw4Q1qXAV1/w9yS
YwwzBZ8O5PHvpsGF7JCBmqKL+sLIR8lNXYSFYMgEQLj4K2kCZv2OT8hbjdE2cPwX
RpjgjSaBEq7Km0L+p1lfPLUlmw9k7LaHV+tiC3wgKYwudSmr139VkplpaHiZrcq9
Cp1eInyLQ2RoVVybUTlcXM3Wh4OWwOLtd8sV+uE3cIlCBVSYTPVJsv6y2nhlux1P
whRrxswPX41HF5ADepczEXetN5JfLPffiB6qLwDU1aWAebkm7ee9OQhcqNdzs3jr
tGkCy66TQdOUvIsyl4fHnlz0ZlSrcsZFzcMXKEWPAkXtnVKRSjTln37ceJjC9f/z
Yzx/Mqi9x6qfUo20MQLBOSPv+OXn+3vHeFqDm2JOIEzS3IcA+1Y0p7SC/giWzPM5
YINmilwtaaC0q/z5bXVR
=vTMh
-END PGP SIGNATURE-



Bug#817211: ITP: ruby-rsync -- ruby wrapper and bindings for the rsync binary

2016-03-08 Thread Sebastien Badia
Package: wnpp
Severity: wishlist
Owner: Sebastien Badia 

* Package name: ruby-rsync
  Version : 1.0.9
  Upstream Author : Joshua Bussdieke
* URL : http://github.com/jbussdieker/ruby-rsync
* License : Expat
  Programming Lang: Ruby
  Description : ruby wrapper and bindings for the rsync binary

 Ruby/Rsync is a Ruby library that can synchronize files between remote
 hosts by wrapping a call to the rsync binary.

This package is a new depdendency of librarian-puppet. And it are going
to be maintained inside the Ruby Team (CCed).