From: Shanthanu <shanthanu.s.rai9@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [GSoC] Query regarding Microproject
Date: Sat, 21 Mar 2020 15:19:20 +0530 [thread overview]
Message-ID: <d676674d-7ab5-b476-8dbb-2b3323db2c89@gmail.com> (raw)
In-Reply-To: <47a1db25-914a-2e59-c0a6-6d0ff77bc2aa@gmail.com>
I found the solution to my issue. The main error message I had got was
> Expected FS format between '1' and '6'; found format '7' at
> {hidden}/git/perl/build/lib/Git/SVN.pm line 310.
After some online searches, I found out that file system format 7
was 'understood' by subversion 1.9 (Filesystem formats section in
https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure).
That's when I realized I was using version 1.9 of subversion.
When I downgraded to subversion 1.8 (which understands file format 6),
all tests passed.
So shouldn't the test file itself have mentioned (say as a comment at
the top
or in a separate README) that it was expecting subversion 1.8 or lesser on
the system? I am using Ubuntu 18.04 and by default the package manager
installs subversion 1.9.
This issue might also be present in other git-svn test files. (I haven't
checked
though, not sure how to run just git-svn tests)
next prev parent reply other threads:[~2020-03-21 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 6:37 [GSoC] Query regarding Microproject Shanthanu Rai
2020-03-20 13:41 ` Christian Couder
2020-03-20 16:27 ` Shanthanu
2020-03-21 9:49 ` Shanthanu [this message]
2020-03-23 19:31 ` Christian Couder
2020-03-25 13:51 ` Shanthanu
-- strict thread matches above, loose matches on Subject: below --
2019-03-05 8:05 [GSOC]:query regarding microproject Sushma Unnibhavi
2019-03-05 21:29 ` Thomas Gummerer
2019-03-04 5:26 [GSoC] Query " Umang Parmar
2019-03-04 7:41 ` Junio C Hamano
2019-03-04 7:52 ` Duy Nguyen
2019-03-04 9:05 ` Christian Couder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d676674d-7ab5-b476-8dbb-2b3323db2c89@gmail.com \
--to=shanthanu.s.rai9@gmail.com \
--cc=christian.couder@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).