[PATCH] Change 'whenCacheOutOfDate' to use '' again.

2014-07-25 Thread Nikita Karetnikov
As some of you may know, I’m trying to make ‘cabal install’ verify OpenPGP signatures that come from Hackage. I modified ‘updatePackageIndexCacheFile’ to ask whether a certain OpenPGP public key should be trusted, but I later discovered that the mentioned function is called twice during ‘cabal

Re: [PATCH] Change 'whenCacheOutOfDate' to use '' again.

2014-07-25 Thread Mikhail Glushenkov
Hi, On 25 July 2014 15:44, Nikita Karetnikov nik...@karetnikov.org wrote: I believe this doesn’t affect #1443 anymore. Why? Have you tested this patch ? ___ cabal-devel mailing list cabal-devel@haskell.org

Re: [PATCH] Change 'whenCacheOutOfDate' to use '' again.

2014-07-25 Thread Nikita Karetnikov
(Oops, resending to the list.) I believe this doesn’t affect #1443 anymore. Why? Have you tested this patch ? I said “believe” because I had to explicitly install process and texmath, but I think that’s not relevant. ‘cabal install --only-dep’ and ‘cabal info pandoc-types-1.12.4’ succeeded

Re: [PATCH] Change 'whenCacheOutOfDate' to use '' again.

2014-07-25 Thread Mikhail Glushenkov
Hi, On 25 July 2014 19:21, Nikita Karetnikov nik...@karetnikov.org wrote: Do you have a better testcase? Why does ‘whenCacheOutOfDate’ run the action on ‘=’ in the first place? If the cache file has the same modification time as the original, it means that the cache is up-to-date, no? OK,

[PATCH] Print a more friendly message when http_proxy is down.

2014-07-25 Thread Nikita Karetnikov
An attempt to fix #1962. I think the exception comes from ‘connect’ in ‘Network.Socket’. I doubt that the proposed error message is friendly enough. Ideas? Also, can ‘handleJust’ catch ‘IOException’s that are not related to http_proxy? From 3a7dbb2391a9b1a262e79d9afecd0ca6a907ce2a Mon Sep 17

Re: [PATCH] Print a more friendly message when http_proxy is down.

2014-07-25 Thread Mikhail Glushenkov
Hi, On 26 July 2014 00:20, Nikita Karetnikov nik...@karetnikov.org wrote: An attempt to fix #1962. I think the exception comes from ‘connect’ in ‘Network.Socket’. Perhaps it's better to solve this in HTTP itself? It gives decent error messages in other cases: $ export HTTP_PROXY=foo $ cabal