# Multiple empty "remote:" lines during remote update 4 messages from 2019-11-18 to 2019-11-18. Participants: Jiri Slaby, Jeff King, Konstantin Ryabitsev. Thread: https://gitlist.dev/t/52282 ## Jiri Slaby, 2019-11-18 08:34 Subject: Multiple empty "remote:" lines during remote update Message-ID: URL: https://gitlist.dev/e/c6b51eaf-79b1-6fb9-6085-2d1a45b739a6%40suse.cz ``` Hi, since some time (weeks or months), I am seeing this: $ git --version git version 2.24.0 $ git remote update Fetching origin remote: remote: remote: remote: remote: remote: remote: remote: remote: Enumerating objects: 7180748, done. remote: remote: remote: remote: remote: remote: remote: remote: Counting objects: 100% (7180748/7180748), done. remote: remote: remote: remote: remote: remote: remote: remote: remote: remote: remote: remote: Compressing objects: 100% (1079308/1079308), done. It looks like the self-overwriting line showing the current state (count of objects, percents, ...) does not work properly. It looks like the part after semicolon is removed, but a newline is emitted anyway. And a new "remote: ..." is printed again. Any ideas? thanks, -- js suse labs ``` ## Jeff King, 2019-11-18 11:44 Subject: Re: Multiple empty "remote:" lines during remote update Message-ID: <20191118114449.GA12766@sigill.intra.peff.net> URL: https://gitlist.dev/e/20191118114449.GA12766%40sigill.intra.peff.net In-Reply-To: ``` On Mon, Nov 18, 2019 at 09:34:46AM +0100, Jiri Slaby wrote: > since some time (weeks or months), I am seeing this: > $ git --version > git version 2.24.0 > $ git remote update > Fetching origin > remote: > remote: This was a bug in v2.22.1, which has been fixed in v2.24.0. However, the bug is on the remote side, so whether you see it depends on which version of Git the server has installed. -Peff ``` ## Jiri Slaby, 2019-11-18 11:59 Subject: Re: Multiple empty "remote:" lines during remote update Message-ID: <90c545c3-4d7c-6d98-a516-e76fe180026e@suse.cz> URL: https://gitlist.dev/e/90c545c3-4d7c-6d98-a516-e76fe180026e%40suse.cz In-Reply-To: <20191118114449.GA12766@sigill.intra.peff.net> ``` On 18. 11. 19, 12:44, Jeff King wrote: > On Mon, Nov 18, 2019 at 09:34:46AM +0100, Jiri Slaby wrote: > >> since some time (weeks or months), I am seeing this: >> $ git --version >> git version 2.24.0 >> $ git remote update >> Fetching origin >> remote: >> remote: > > This was a bug in v2.22.1, which has been fixed in v2.24.0. However, the > bug is on the remote side, so whether you see it depends on which > version of Git the server has installed. OK, thanks. $ git remote -v origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git (fetch) origin git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git (push) CCing Konstantin, in case he does not know yet... thanks, -- js suse labs ``` ## Konstantin Ryabitsev, 2019-11-18 13:35 Subject: Re: Multiple empty "remote:" lines during remote update Message-ID: <20191118133536.u3k7kkucw6mz7jlv@chatter.i7.local> URL: https://gitlist.dev/e/20191118133536.u3k7kkucw6mz7jlv%40chatter.i7.local In-Reply-To: <90c545c3-4d7c-6d98-a516-e76fe180026e@suse.cz> ``` On Mon, Nov 18, 2019 at 12:59:52PM +0100, Jiri Slaby wrote: > On 18. 11. 19, 12:44, Jeff King wrote: > > On Mon, Nov 18, 2019 at 09:34:46AM +0100, Jiri Slaby wrote: > > > >> since some time (weeks or months), I am seeing this: > >> $ git --version > >> git version 2.24.0 > >> $ git remote update > >> Fetching origin > >> remote: > >> remote: > > > > This was a bug in v2.22.1, which has been fixed in v2.24.0. However, the > > bug is on the remote side, so whether you see it depends on which > > version of Git the server has installed. > > OK, thanks. > > $ git remote -v > origin > git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git > (fetch) > origin > git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git (push) > > CCing Konstantin, in case he does not know yet... I'm aware of it, but I'm hoping IUS starts providing either a patched git222 package, or a new git-224 package where this bug is fixed. Since it's a purely cosmetic problem, I don't want to patch it locally. CCing devs at IUS for their info. -K ```