Closed ghost closed 10 years ago
I think you should delete your C:\Users\%USERNAME%\AppData\Roaming\cabal\packages\
, then cabal update
. This could cause problems with other installed packages, so beware. The archives tar seems corrupt, potentially from a strange network cache, ISP mitm or network interruption.
I think the problem is related to the two questions I recently posted on Stack Overflow:
1) http://stackoverflow.com/questions/21800590/problems-with-cabal-install-cabal-install-in-windows http://stackoverflow.com/questions/21800590/problems-with-cabal-install-cabal-install-in-windows
2) http://stackoverflow.com/questions/21366775/cabal-fails-updating-of-cabal-install http://stackoverflow.com/questions/21366775/cabal-fails-updating-of-cabal-install
Let me start by saying that "C:\Program Files (x86)\HaskellPlatform\2013.2.0.0\lib\extralibs\cabal.exe" was deleted to access to the updated cabal.exe (see the note 1 above)
After I have deleted “PATH = C:\Users\Alberto\AppData\Roaming\cabal\packages\”, launched (from its directory) “cabal update” than “cabal install tables”, the result was unchanged:
C:\Users\Alberto\AppData\Roaming\cabal\bin>cabal update
Downloading the latest package list from hackage.haskell.org
C:\Users\Alberto\AppData\Roaming\cabal\bin>cabal install tables
Resolving dependencies...
cabal: internal error when reading package index: could not read tar file
entryThe package index or index cache is probably corrupt. Running cabal
update might fix it.
From: Maxwell Swadling [mailto:notifications@github.com] Sent: 16 February 2014 14:50 To: ekmett/tables Cc: acapitani Subject: Re: [tables] Problems installing tables with cabal install (#24)
I think you should delete your C:\Users\%USERNAME%\AppData\Roaming\cabal\packages\, then cabal update. This could cause problems with other installed packages, so beware. The archives tar seems corrupt, potentially from a strange network cache, ISP mitm or network interruption.
— Reply to this email directly or view it on GitHub https://github.com/ekmett/tables/issues/24#issuecomment-35197102 . https://github.com/notifications/beacon/6522254__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwODA5MTQxNCwiZGF0YSI6eyJpZCI6MjU3NDk5NjJ9fQ==--c3d652e42284a36fe2679f49a1b47ba928566c79.gif
I tried to install "tables" using version version 1.16.0 of the Cabal library and all went well.
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Alberto>cabal -V cabal-install version 1.16.0.2 using version 1.16.0 of the Cabal library
C:\Users\Alberto>cabal install tables Resolving dependencies... Downloading cereal-0.3.5.2... Configuring cereal-0.3.5.2... ... etc. ... Loading package binary-0.7.1.0 ... linking ... done. In-place registering tables-0.4... Installing library in C:\Users\Alberto\AppData\Roaming\cabal\tables-0.4\ghc-7.6.3 Registering tables-0.4... Installed tables-0.4
C:\Users\Alberto>
This appears to be a cabal issue, rather than a tables issue.
A similar issue has popped up for me in the past on an unrelated package when I pulled cabal update
from behind a firewall that transparently un-gzipped the package list to be "helpful".
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Alberto>cabal update Downloading the latest package list from hackage.haskell.org
C:\Users\Alberto>cabal install tables Resolving dependencies... cabal: internal error when reading package index: could not read tar file entryThe package index or index cache is probably corrupt. Running cabal update might fix it.
C:\Users\Alberto>cabal install lens (JUST TO TEST...) Resolving dependencies... All the requested packages are already installed: lens-4.0 Use --reinstall if you want to reinstall anyway.
--- AND AGAIN
C:\Users\Alberto>cabal update Downloading the latest package list from hackage.haskell.org
C:\Users\Alberto>cabal install tables Resolving dependencies... cabal: internal error when reading package index: could not read tar file entryThe package index or index cache is probably corrupt. Running cabal update might fix it.
C:\Users\Alberto>