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 <allber...@gmail.com> wrote: > 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 Collins <nathan.coll...@gmail.com> > wrote: > >> In case this confuses anyone else, I think this PSA only applies if >> you're using cabal-install version 2.*, but please correct me if I'm >> wrong. >> >> 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. Then I noticed I was using cabal-install version 1.24.0.2. When >> I upgraded to cabal-install version 2.0.0.1 and did another `cabal >> update` the 01-index.* files appeared. >> >> Cheers, >> >> -nathan >> >> On Mon, Jan 1, 2018 at 5:24 PM, Gershom B <gersh...@gmail.com> wrote: >> > 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 >> > file in place. It is easy to get things working again, but it requires >> > manual intervention. Here is the most straightforward way to get >> > things working again: >> > >> > On gnu/linux or mac: rm ~/.cabal/packages/ >> hackage.haskell.org/01-index.* >> > On windows: remove the same files, but from >> > %appdata%\cabal\packages\hackage.haskell.org >> > >> > rerun `cabal update` to fetch a new 01-index. >> > >> > Apologies all for the inconvenience and any confusion this may have >> > caused. There is a PR to fix this behavior in the works, but since the >> > problem is on the client side, the fix will only improve the >> > situations for new versions of `cabal`. >> > >> > Happy New Years to all, and cheers to a very functional 2018, >> > Gershom >> > >> > p.s.: since the problem comes in unpacking the 01-index.tar.gz into >> > the 01-index.tar, you can also just untar that file in place manually, >> > or force cabal into doing the same by running `touch >> > ~/.cabal/packages/hackage.haskell.org/01-index.tar` >> <http://hackage.haskell.org/01-index.tar> >> > _______________________________________________ >> > Haskell-Cafe mailing list >> > To (un)subscribe, modify options or view archives go to: >> > http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe >> > Only members subscribed via the mailman list are allowed to post. >> _______________________________________________ >> Haskell-Cafe mailing list >> To (un)subscribe, modify options or view archives go to: >> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe >> Only members subscribed via the mailman list are allowed to post. > > > > > -- > brandon s allbery kf8nh sine nomine > associates > allber...@gmail.com > ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users >
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users