From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Michael <aixtools@felt.demon.nl>
Cc: git@vger.kernel.org
Subject: Re: git broken for AIX somewhere between 2.13.2 and 2.13.3
Date: Sun, 29 Jul 2018 18:10:06 +0000 [thread overview]
Message-ID: <20180729181006.GC945730@genre.crustytoothpaste.net> (raw)
In-Reply-To: <fb935882-25b1-db5f-d765-50dab297f733@felt.demon.nl>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On Sun, Jul 29, 2018 at 06:44:26PM +0200, Michael wrote:
> root@x066:[/tmp/xxx]git --version
> git version 2.13.3
> root@x066:[/tmp/xxx]git clone git@github.com:aixtools/hello-world.git
> Cloning into 'hello-world'...
> remote: Counting objects: 3, done.
> remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 3
> Receiving objects: 100% (3/3), done.
> fatal: pack is corrupted (SHA1 mismatch)
> fatal: index-pack failed
>
> p.s. - what surprises me re: git-2.13.2 - no messages about 'Cloning into
> ...', which version 2.13.1 did give.
>
> I guess a bisect is the next step - between version 2.13.2 and 2.13.3. Other
> suggestions welcome!
Are you using SHA1DC on that system, and does compiling with another
SHA-1 implementation help? There was a change to the SHA1DC code big
endian detection in that commit, which might be the cause of your
problems if you're using a POWER or PowerPC system.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 867 bytes --]
next prev parent reply other threads:[~2018-07-29 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 16:44 git broken for AIX somewhere between 2.13.2 and 2.13.3 Michael
2018-07-29 18:10 ` brian m. carlson [this message]
2018-07-29 19:46 ` Michael
2018-07-29 20:05 ` Ævar Arnfjörð Bjarmason
2018-07-29 21:40 ` Andreas Schwab
2018-07-30 6:22 ` Michael
[not found] ` <2309fa7f-c2d8-ee57-aff5-b9e32d2da609@felt.demon.nl>
[not found] ` <20180729192753.GD945730@genre.crustytoothpaste.net>
2018-07-29 19:48 ` Michael
2018-07-29 20:06 ` brian m. carlson
2018-07-29 20:50 ` Michael
2018-07-30 9:39 ` Is detecting endianness at compile-time unworkable? Ævar Arnfjörð Bjarmason
2018-07-30 14:54 ` Junio C Hamano
2018-07-30 18:32 ` Junio C Hamano
2018-07-30 18:39 ` Daniel Shumow
2018-07-31 10:06 ` Michael Felt
2018-08-01 1:35 ` Eric Wong
2018-08-01 7:16 ` Ævar Arnfjörð Bjarmason
2018-07-31 10:39 ` Michael Felt
2018-08-01 7:31 ` Ævar Arnfjörð Bjarmason
2018-08-02 20:50 ` [PATCH] sha1dc: update from upstream Ævar Arnfjörð Bjarmason
2018-08-02 21:29 ` Michael Felt (aixtools)
2018-08-02 21:32 ` Stefan Beller
2018-07-31 12:32 ` Is detecting endianness at compile-time unworkable? Michael Felt
2018-07-31 14:01 ` Michael Felt
2018-07-31 14:25 ` Ævar Arnfjörð Bjarmason
2018-07-31 20:06 ` Michael
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180729181006.GC945730@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=aixtools@felt.demon.nl \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).