I noticed that after upgrading to git-2.23.0, a simple clone (tested using git/ssh protocol) git clone git@myserver:/path/to/repo Results in lots of empty remote: lines printed to stdout. The nice folks in #git on freenode pointed me at a ML discussion here: https://public-inbox.org/git/20190822141928.GA3163@323642-phi-gmno-clahs/ I worked around the issue by applying the patch from upstream commit: bbf47568ad7e91ab0962b314c054a2da03232c72 and rebuilding git-2.23.0. This was only required on the server, not the client(s). I'm not suggesting anything get done about this in Gentoo, since it will be included in git-2.24.0, but merely adding a tracker in case someone else hits it and searches bugs.gentoo. You can also work around just by holding git back to 2.21.0. Reproducible: Always
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=23dafc624b8f4269cd3da2104528cb5fa3cda81d commit 23dafc624b8f4269cd3da2104528cb5fa3cda81d Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2019-10-26 12:54:34 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2019-10-26 12:54:34 +0000 dev-vcs/git: Revbump to avoid empty "remote" output from git servers Bumped straight to stable Thanks-to: David Flogeras <dflogeras2@gmail.com> Closes: https://bugs.gentoo.org/698384 Package-Manager: Portage-2.3.78, Repoman-2.3.17 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> .../files/git-2.23.0-avoid_empty_remote_line.patch | 145 +++++++++++++++++++++ .../{git-2.23.0.ebuild => git-2.23.0-r1.ebuild} | 2 + 2 files changed, 147 insertions(+)
