From: "Greg A. Woods" <woods@planix.com>
To: The Git Mailing List <git@vger.kernel.org>
Subject: odd "error: packfile foo.pack cannot be accessed" errors from "git svn fetch"
Date: Mon, 26 Apr 2010 18:06:56 -0400 [thread overview]
Message-ID: <m1O6WSB-000kn6C@most.weird.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
I've been trying to import the FreeBSD SVN repository (which I have
copied to a local directory using "svnsync"). It seems to be going
fairly well, though I've had to interrupt and restart the "git svn fetch
--all" command a couple of times due to necessary reboots.
However I noticed errors similar to the following today as it was
running, particularly between these revision lines:
r158178 = dfd866111e2d8b27056d445ce1109ca3301f7dda (refs/remotes/svn/stable/6)
A usr.bin/lastcomm/lastcomm.c
A usr.bin/lastcomm/pathnames.h
[[....]]
error: packfile ./objects/pack/pack-a65415929f8bae9dacf4e81a3d9201135915c984.pack cannot be accessed
[[....]]
A sys/sys/msg.h
A sys/sys/socket.h
r158179 = db56f27606a021514e1f8ec483ce6b7abd4d6966 (refs/remotes/svn/releng/6.1)
(this is from git version 1.7.0.6, running on Mac OS X 10.6.3 with all
files on an HFS+ case-sensitive journaled filesystem)
Several such lines were printed, all while adding the same revision,
with several different pack files mentioned.
Was it my mistake to interrupt the fetch? (I assumed interrupts would
be cleanly handled -- they really should be, nay must be if git-svn is
to be robust enough for real-world uses! I don't do perl, though I had
a peek and did see at least some mention of SIGINT....)
Is there any way to check the integrity of the result other than by
manually checking out various releases from each SVN and Git and
comparing them?
I could start it over again in a hopefully more stable environment if
really necessary, but it's already run for over two days now, and
already this isn't my first attempt (getting the branches config close
to correct has been far more difficult than it should ever have been --
this info is already in SVN! hopefully the GSoC native SVN support will
help in this regard too!)
--
Greg A. Woods
Planix, Inc.
<woods@planix.com> +1 416 218 0099 http://www.planix.com/
[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]
next reply other threads:[~2010-04-26 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 22:06 Greg A. Woods [this message]
2010-04-27 20:22 ` odd "error: packfile foo.pack cannot be accessed" errors from "git svn fetch" Greg A. Woods
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=m1O6WSB-000kn6C@most.weird.com \
--to=woods@planix.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.