Quoth Nathan Collins ,
> I had some ~/.cabal/packages/hackage.haskell.org/00-index.* files, but
> not any 01-index.* files, and running `cabal update` didn't change
> that.
I see this when using hackage.fpcomplete.com, rather than hackage.haskell.org.
(The latter is very slow for me, and sometim
My cabal v2 seemed to be using 00 indices. Much to my confusion. Maybe I
should reinstall it and check my config ;)
On Thu, Jan 4, 2018 at 5:25 PM Brandon Allbery wrote:
> Correct: cabal-install 1.x still uses the old index format (00-index). The
> logic is different for 01-index, in order to
Correct: cabal-install 1.x still uses the old index format (00-index). The
logic is different for 01-index, in order to support incremental update
(appending when possible, instead of always having to download the whole
thing again like with 00-index).
On Thu, Jan 4, 2018 at 1:38 PM, Nathan Collin
On Tue, Jan 2, 2018 at 11:47 AM, Sven Panne wrote:
> 2018-01-02 2:24 GMT+01:00 Gershom B :
>
>> A recent update to hackage, which fixed up the 01-index.tar.gz file,
>> revealed a bug in existing versions of cabal-install, when index files
>> are cleaned up. This bug means that the `cabal update`
2018-01-02 2:24 GMT+01:00 Gershom B :
> A recent update to hackage, which fixed up the 01-index.tar.gz file,
> revealed a bug in existing versions of cabal-install, when index files
> are cleaned up. This bug means that the `cabal update` command, which
> updates the hackage index file, will fail
Dear Haskellers,
A recent update to hackage, which fixed up the 01-index.tar.gz file,
revealed a bug in existing versions of cabal-install, when index files
are cleaned up. This bug means that the `cabal update` command, which
updates the hackage index file, will fail silently and leave the old
fi
