From: "J.H." <warthog9@eaglescrag•net>
To: Severin Gehwolf <jerboaa@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [Bug] Gitweb corrupting files?
Date: Wed, 12 Jan 2011 09:08:54 -0800 [thread overview]
Message-ID: <4D2DE026.4080109@eaglescrag.net> (raw)
In-Reply-To: <AANLkTim84sSWr=WRgjiY=Y3Mq7Tgojv9CpLrNjQMJfHR@mail.gmail.com>
On 01/12/2011 08:05 AM, Severin Gehwolf wrote:
> Hi,
>
> It appears that Gitweb corrupts files when it is being used for
> creating compressed tarballs of sources.
>
> A more precise description of the behaviour I'm experiencing is here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=317882
>
> Unfortunately I have no knowledge about the version in use at eclipse.org.
That's a fairly old version of gitweb running (1.6.6.4), and it looks
like it's stock gitweb (I.E. not the caching version). The file itself
(the .bz2 anyway) is a valid, and complete .bz2, as well as the .tar
file extracts cleanly.
That would indicate, that if there is corruption, it is happening in the
git process itself that generates the tarball, and not in gitweb itself.
Best plan would be to upgrade to the latest code of gitweb and git and
see if the problem still persists, and if it does be able to get us a
tarball and url that has the corruption.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2011-01-12 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 16:05 [Bug] Gitweb corrupting files? Severin Gehwolf
2011-01-12 17:08 ` J.H. [this message]
2011-01-12 18:05 ` Jakub Narebski
2011-01-15 15:39 ` [Not a] " Severin Gehwolf
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=4D2DE026.4080109@eaglescrag.net \
--to=warthog9@eaglescrag$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=jerboaa@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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