(Last) Monday triage report (2020-09-21)

[Sergio Durigan Junior]

On Monday, September 28 2020, I wrote:

> ### https://pad.lv/1896251 - (New) [rsync] - rsync --delete-missing-args
>     fails with error: protocol incompatibility
>
> Investigated and confirmed that the problems happens on Xenial, Bionic
> and Focal, so I added these targets and marked them as Triaged.
> I also found the upstream commit that "fixes" the bug.  I said "fixes"
> in quotes because what the commit does is to make the rsync on
> Xenial/Bionic/Focal behave like the one on Groovy (and Debian sid),
> which is still giving me an error (a different one) when I run the
> user's command.  One would have to investigate whether the error is yet
> another bug, or is expected, or...  Anyway, I tagged the bug as
> server-next since it is a valid bug, and also subscribe Ubuntu Server.

After an interesting off-list discussion with Robie, I went ahead and
untagged server-next in the bug above.

The initial reason I had tagged it as server-next is that I had the
impression that (a) the bug is relatively well understood, has a
candidate patch which likely fixes the problem, and (b) there are
similar bug reports against upstream, Fedora and Debian rsyncs, so maybe
we could infer that it affects multiple users (albeit not multiple
Ubuntu users, since only one has reported it).

The reason I decided to untag the bug is because just one user seemed
bothered enough to report a bug, and even though I did find a commit
that likely fixes the bug, I also think that there might be another bug
hidden.  On top of that we are also short on resources for the next
cycle, so I believe (or it is my impression, at least) that we should be
a bit more rigid when promoting a bug to server-next.

Thanks,

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14