Opened 7 years ago
Closed 7 years ago
#54786 closed defect (duplicate)
git @2.14.1_1: SHA1 mismatch when cloning repo
Reported by: | rickyzhang82 (Ricky Zhang) | Owned by: | ci42 |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.1 |
Keywords: | tiger | Cc: | |
Port: | git |
Description
Recently I upgrade macport in Tiger PPC. Upgrading git from @2.9.3_0+credential_osxkeychain+doc+pcre+perl5_22+python27 to @2.14.1_1+credential_osxkeychain+doc+pcre+perl5_24 cause a strange error when cloning repo.
It alarmed SHA1 mismatch. I don't know if git itself compute SHA1 checksum or it uses 3rd party library. Any ideas?
git clone --progress git://repo.or.cz/qgit4/redivivus.git Cloning into 'redivivus'... remote: Counting objects: 7471, done. remote: Compressing objects: 100% (3028/3028), done. remote: Total 7471 (delta 5767), reused 5653 (delta 4421) Receiving objects: 100% (7471/7471), 1.93 MiB | 347.00 KiB/s, done. fatal: pack is corrupted (SHA1 mismatch) fatal: index-pack failed Ricky@pg4:/tmp$ sudo port activate git The following versions of git are currently installed: 1) git @2.9.3_0+credential_osxkeychain+doc+pcre+perl5_22+python27 2) git @2.14.1_1+credential_osxkeychain+doc+pcre+perl5_24 (active) Enter a number to select an option: 1 ---> Deactivating git @2.14.1_1+credential_osxkeychain+doc+pcre+perl5_24 ---> Cleaning git ---> Activating git @2.9.3_0+credential_osxkeychain+doc+pcre+perl5_22+python27 Ricky@pg4:/tmp$ git clone --progress git://repo.or.cz/qgit4/redivivus.git Cloning into 'redivivus'... remote: Counting objects: 7471, done. remote: Compressing objects: 100% (3028/3028), done. remote: Total 7471 (delta 5769), reused 5652 (delta 4421) Receiving objects: 100% (7471/7471), 1.92 MiB | 386.00 KiB/s, done. Resolving deltas: 100% (5769/5769), done. Checking connectivity... done.
Change History (4)
comment:1 Changed 7 years ago by rickyzhang82 (Ricky Zhang)
comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | tiger added |
---|---|
Owner: | set to ci42 |
Status: | new → assigned |
Is there an upstream git or openssl bug report about this problem that you could refer us to?
comment:4 Changed 7 years ago by mf2k (Frank Schima)
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
I believe the culprit is openssl package. But I haven't figured it out how to fix it.