Bug#1101076: ITP: rsync -- rsync in Go! implements client and server, which can send or receive files (upload, download, all directions supported)

[Samuel Henrique]

Package: wnpp
Severity: wishlist
Owner: Samuel Henrique <***@debian.org>
X-Debbugs-CC: debian-***@lists.debian.org, debian-***@lists.debian.org

* Package name : rsync
Version : 0.2.6-1
Upstream Author : Michael Stapelberg <stapelberg>
* URL : https://github.com/gokrazy/rsync
* License : BSD-3-clause
Programming Lang: Go
Description : rsync in Go! implements client and server, which can send or receive files (upload, download, all directions supported)

Given the current status of the maintenance on rsync upstream, it's
going to be handy to have an alternative packaged in the repository just
in case.

I haven't played much with this software yet, but I plan to package it
for forky.

Thank you,

--
Samuel Henrique <samueloph>

[Simon McVittie]

Post by Samuel Henrique
* Package name : rsync

This is going to need a different name, unless you are aiming for it to
completely replace and supersede the original (samba.org) rsync.

Upstream seems to call their main executable gokr-rsync, which seems as
good a name for the package as any other?

smcv

[Antonio Russo]

[not sending to the ITP bug, since it is off-topic for that]

Post by Samuel Henrique
Given the current status of the maintenance on rsync upstream, it's
going to be handy to have an alternative packaged in the repository just
in case.

Could you elaborate on the state of rsync upstream? I have never had
any problem with rsync personally, and they appear to have made three
releases in the last 12 months. Superficially, it looks like software
that is approaching its platonic ideal: unchanging and bug-free.

Granted, I know nothing about this except it's a silent piece of my
infrastructure that has always "just worked." Is there an article
about this, what is going wrong, and/or what needs to be done?

Thanks,
Antonio Russo