From: Daniel Marschall <info@daniel-marschall.de>
To: git@vger.kernel.org
Subject: git-svn bug: Output git directory has uncommitted changes
Date: Sun, 24 Oct 2021 22:11:46 +0200 [thread overview]
Message-ID: <77aacb3b44523223c7647bdae1702a31@daniel-marschall.de> (raw)
Hello,
I have found following bug in the latest version of git-svn . I have
this issue with the old version shipped in Debian stable, as well as
with the latest version built from source.
What did you do before the bug happened? (Steps to reproduce your issue)
Extract the following SVN repository to GIT:
https://svn.viathinksoft.com/svn/filter_foundry/
The bug ONLY happens with this single SVN repository. All other SVN
repositories from my server work perfectly.
$ PERL5LIB=perl/ ./git-svn --authors-file="../../authors.txt" clone
--trunk="trunk" "https://svn.viathinksoft.com/svn/filter_foundry/"
"_test"
$ cd _test
$ git status
What did you expect to happen? (Expected behavior)
git status should show that nothing needs to be commited.
What happened instead? (Actual behavior)
You get a long list of files which need to be committed. The list is
sometimes longer and sometimes shorter. So, the behavior is not
deterministic. I have the feeling that the list often contains all files
in the repo.
Anything else you want to add:
This SVN repository was cloned from a foreign server to my own server,
and then continued there. I think this SVN repository has some specific
properties that cause the bugs.
Authors.txt file (changed email addresses for privacy reasons):
daniel-marschall = Person 1 <person1@example.com>
www-data = Person 2 <person2@example.com>
root = Person 3 <person3@example.com>
toby = Person 4 <person4@example.com>
ddenk = Person 5 <person5@example.com>
peter = Person 6 <person6@example.com>
dmarschall = Person 7 <person7@example.com>
[System Info]
git version:
git version 2.33.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18)
x86_64
compiler info: gnuc: 8.3
libc info: glibc: 2.28
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
not run from a git repository - no hooks to show
next reply other threads:[~2021-10-24 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 20:11 Daniel Marschall [this message]
2021-10-25 9:41 ` git-svn bug: Output git directory has uncommitted changes Eric Wong
2021-10-26 15:14 ` Torsten Bögershausen
2021-10-26 19:30 ` Daniel Marschall
2021-10-27 14:41 ` Torsten Bögershausen
2021-10-30 20:52 ` Daniel Marschall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77aacb3b44523223c7647bdae1702a31@daniel-marschall.de \
--to=info@daniel-marschall.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).