From: Thomas Rast <trast@student.ethz.ch>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: git list <git@vger.kernel.org>, Jonas Thiem <contact@eloxoph.com>
Subject: Re: Remote corruption issue, linked to thin pack code?
Date: Thu, 26 Aug 2010 09:13:59 +0200 [thread overview]
Message-ID: <201008260914.00741.trast@student.ethz.ch> (raw)
In-Reply-To: <alpine.LFD.2.00.1008252107070.622@xanadu.home>
Nicolas Pitre wrote:
> > The respective repos show no errors with git-fsck.
>
> What about 'git fsck --full'? Given git v1.5.4 on the remote, you
> should try --full with 'git fsck' as this wasn't the default back then.
Well, I instructed him to try --full, as you can see in the
conversation:
http://colabti.org/irclogger/irclogger_log/git?date=2010-08-25#l2196
Nothing interesting.
> > http://eloxoph.com/localrepo.zip
> > http://eloxoph.com/remoterepo.zip
>
> 2010-08-25 21:24:52 ERROR 404: Not Found.
Hrm. Apparently a mis-edit on my part, it should be
http://eloxoph.com/remoteserverrepo.zip
> How do you know it is there while git (on the remote) is telling you it
> is not?
>
> What about 'git cat-file -t e28ae6b61c384732c506' ?
It's fine in my unpacked copy. Jonas, what were the results on the
server?
> Maybe after I can reproduce this issue locally.
As a side note, I couldn't reproduce locally with the above repos but
then I didn't have the time to downgrade to 1.5.4.
Jonas also has to answer the rest of the questions for obvious
reasons. (I'm away from the net for a few days anyway...)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2010-08-26 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:53 Remote corruption issue, linked to thin pack code? Thomas Rast
2010-08-26 2:42 ` Nicolas Pitre
2010-08-26 7:13 ` Thomas Rast [this message]
2010-08-26 10:13 ` Jonas Thiem
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=201008260914.00741.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=contact@eloxoph.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/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).