From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Thomas Glanzmann" <thomas@glanzmann.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Nicolas Pitre" <nico@cam.org>, GIT <git@vger.kernel.org>,
"Michael Gernoth" <simigern@cip.informatik.uni-erlangen.de>
Subject: Re: fatal: serious inflate inconsistency
Date: Sun, 10 Jun 2007 12:50:07 +1200 [thread overview]
Message-ID: <46a038f90706091750x446c96bfkdc1d5dd0cc59e5d2@mail.gmail.com> (raw)
In-Reply-To: <20070608193319.GS2335@cip.informatik.uni-erlangen.de>
On 6/9/07, Thomas Glanzmann <thomas@glanzmann.de> wrote:
> I have a very similar machine. For this one it works. It has 32 bit kernel and
> userland. Debian etch again. v2.6.20.
Wanted to mention -- we've been using git on debian sarge/etch on
several arches a lot and never seen any lib compatiblity problem.
> Does someone know a command for debian that checks the checksums
apt-get install debsums
man debsums # sorry, I don't use it often enough to remember ;-)
cheers,
m
next prev parent reply other threads:[~2007-06-10 0:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 11:05 fatal: serious inflate inconsistency Thomas Glanzmann
2007-06-08 13:48 ` Nicolas Pitre
2007-06-08 13:50 ` Thomas Glanzmann
2007-06-08 15:37 ` Thomas Glanzmann
2007-06-08 15:39 ` Thomas Glanzmann
2007-06-08 16:15 ` Nicolas Pitre
2007-06-08 17:01 ` Linus Torvalds
2007-06-08 18:24 ` Thomas Glanzmann
2007-06-08 18:52 ` Linus Torvalds
2007-06-08 19:06 ` Linus Torvalds
2007-06-08 19:33 ` Thomas Glanzmann
2007-06-08 20:45 ` Marco Roeland
2007-06-09 0:13 ` Thomas Glanzmann
2007-06-09 21:12 ` Thomas Glanzmann
2007-06-10 0:30 ` Linus Torvalds
2007-06-10 0:50 ` Martin Langhoff [this message]
2007-06-17 8:01 ` Thomas Glanzmann
-- strict thread matches above, loose matches on Subject: below --
2007-11-09 14:14 bob
2007-11-09 16:11 ` Nicolas Pitre
2007-11-09 18:06 ` bob
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=46a038f90706091750x446c96bfkdc1d5dd0cc59e5d2@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=simigern@cip.informatik.uni-erlangen.de \
--cc=thomas@glanzmann.de \
--cc=torvalds@linux-foundation.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 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).