From: Junio C Hamano <junkio@cox.net>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: git@vger.kernel.org
Subject: Re: FW: Git pulls failing on ia64 test tree?
Date: Wed, 14 Sep 2005 10:25:31 -0700 [thread overview]
Message-ID: <7vk6hjlfxw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vbr2vob6w.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Wed, 14 Sep 2005 09:39:51 -0700")
Junio C Hamano <junkio@cox.net> writes:
> "Luck, Tony" <tony.luck@intel.com> writes:
>
>> I've set up objects/info/alternates to point at linus' tree and deleted
>> all the packs from my tree. The web view at kernel.org/git looks ok,
>> so I think those changes are ok.
>>
>> So what am I missing?
>
> Let me take a look at your tree on master while I'll try to pull
> from your public tree and see if I can reproduce.
Ah, you deleted packs from your repository, which I missed when
I first saw your message.
The objects/info/alternates mechanism is currently only known to
the git that operates on the machine that has the file -- client
side does not make use of that information. That means only
git-daemon and 'git native protocol over ssh' (not the commit
walker ssh-fetch) can deal with such a repository right now,
because they run git on the side your repository is. Gitweb
also obviously runs git on the machine a copy of repository is,
so you would not see problems.
The recommendation by Linus to "point him with alternate to
borrow his objects" is a sound one in the long term, but I think
it was a bit premature in practice -- the client side tools are
not ready for that yet. From the original error report:
> error: Could not read 9401c705f2a6a7e5df102f6443dba395c3c5e5a8
> error: Could not read 357d596bd552ad157a906289ab13ea6ba7e66e3d
> Updating from aa2dca4563b0629ecd9d9994dfdf39f29ff1b43f to
6c141f61ee4f5fba63d9c54e03cb2faa6877bf1a.
> fatal: failed to unpack tree object 6c141f61ee4f5fba63d9c54e03cb2faa6877bf1a
> $
The first two "Could not read" are talking about objects only
found in Linus' repository -- your objects/ hierarchy does not
have them. Rsync transport slurps everything under _your_
objects/ hierarchy [*1*] and does not know that your objects/
hierarchy is incomplete and needs to borrow from Linus' objects/
directory. If the downloader has the objects found in Linus'
repository that is fine but otherwise he has problems.
As a workaround, please do this:
cd /pub/scm/linux/kernel/git/aegl/linux-2.6.git/
ln ../../torvalds/linux-2.6.git/objects/pack/* objects/pack/.
mv objects/info/alternates objects/info/alternates+
GIT_DIR=. git fetch ../../torvalds/linux-2.6.git/
GIT_DIR=. git fsck-objects
mv objects/info/alternates+ objects/info/alternates
The 'git fetch' step would complain about a couple of commits
you have but there is no need to worry -- we are deliberately
"corrupting" your repository by temporarily moving alternates
away so that it can fetch missing objects from Linus repository.
The fsck-objects should then report no missing objects.
Sorry for this very unpleasant experience git has caused you
X-<.
[Footnotes]
*1* BTW, I just spotted a bug there -- since we now have
objects/info subdirectory, we should exclude that when copying.
*2* Ideally I would have liked to do git-relink after 'git fetch'
from Linus repo in the above, but it does not seem to want to
relink a naked repository... I should bug Ryan about it.
next prev parent reply other threads:[~2005-09-14 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 15:47 FW: Git pulls failing on ia64 test tree? Luck, Tony
2005-09-14 16:39 ` Junio C Hamano
2005-09-14 17:25 ` Junio C Hamano [this message]
2005-09-14 17:47 ` Junio C Hamano
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=7vk6hjlfxw.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).