August 2012 - cabal-devel

patch applied (hackage-server): "Add another stat" and 1 others
by devnull＠community.haskell.org 17 Aug '12

17 Aug '12

Fri Aug 17 23:49:38 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Add another stat Ignore-this: b7cb57cf2bbbbce68aad1eda8d044bb7 M ./BuildClient.hs +2 Sat Aug 18 00:13:27 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Define Cabal's logs-dir in the doc builder Ignore-this: aacaf1155247c6eabbb5b89f1108e567 M ./BuildClient.hs +1

1 0

patch applied (hackage-server): "Doc builder improvements" and 1 others
by devnull＠community.haskell.org 17 Aug '12

17 Aug '12

Fri Aug 17 20:32:17 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Doc builder improvements Ignore-this: c5a63b43eaffa7f29ffe7a9b68483754 We now put all the stuff we generate while haddocking a package inside a single "inst" directory so that we can clean it easily. We also pass --no-user-package-conf to ghc-pkg so that we don't have "packages are likely to be broken by the reinstalls" warnings all the time. M ./BuildClient.hs -33 +44 Fri Aug 17 22:02:41 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Add a "stats" command to the doc builder Ignore-this: 60a72fea921b1b6b989e49d6b2b1fef3 It tells you how many packages have docs already built M ./BuildClient.hs -2 +67

1 0

Automatic package reconfiguration and ConfigExFlags
by Thomas Tuegel 16 Aug '12

16 Aug '12

Hello! Today I merged commits for automatic reconfiguration and rebuilding of a package as necessary when 'cabal test' and 'cabal bench' are invoked. The automatic reconfiguration code is based on the code already used to reconfigure packages when './Setup build' and 'cabal build' are invoked. I noticed that the existing reconfiguration code does not account for ConfigExFlags that may have been passed to 'cabal configure' the last time the package was configured. (My alterations do not affect this behaviour.) The purpose of this message is to bring attention to the problems I think this could cause and with the help of the community, determine the actual severity of the issue. Then we can decide if/when and how to resolve it. Obviously, if Cabal is being invoked through a 'Setup' script, there is no need for concern. However, ConfigExFlags affect dependency resolution during configuration, so automatic reconfiguration that ignores them may silently and unexpectedly change how the package is linked. I'm concerned this could (hypothetically) lead to linking to a different version of a dependency, causing build failure (or worse, if different versions of the dependency have different behaviours). I also have some reason to believe the situation is not that dire. After the initial configuration, the resolved dependencies are saved in the ConfigFlags in the LocalBuildInfo. When reconfiguring, the worst possible outcome should be that the dependency resolver cannot resolve the given dependencies and versions without some ConfigExFlags that would now be missing. To get my patches merged, I ignored this issue. The easiest solution is simply to include the ConfigExFlags in the LocalBuildInfo. That is something that could be done when/if the 'Setup' script builds actually become deprecated, since the ConfigExFlags reside in cabal-install, but the LocalBuildInfo is in Cabal. We may want to take care of this in the short term, but on the other hand, it could probably wait: this is far from a new issue, and I can't document any case of someone actually bitten by this bug. Feel free to tell me I'm making this out to be more than it is, but I thought I should present it before the community. Thanks! -- Thomas Tuegel

3 4

patch applied (hackage-server): "Tweak create-doc-builder-vm.txt" and 1 others
by devnull＠community.haskell.org 16 Aug '12

16 Aug '12

Thu Aug 16 22:17:08 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Tweak create-doc-builder-vm.txt Ignore-this: 395ea9362612aaeea4ea34a7cd0b7d50 M ./docs/create-doc-builder-vm.txt -1 +1 Thu Aug 16 22:18:48 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Add / to the end of doc URLs Ignore-this: e940a5d3ebde1a1f422a8a26bc6bb520 This saves having to do "GET .../doc" and get a 301 before requesting the real URL for each package. M ./BuildClient.hs -1 +1

1 0

patch applied (hackage-server): "Tweak doc builder instructions"
by devnull＠community.haskell.org 16 Aug '12

16 Aug '12

Thu Aug 16 21:44:31 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Tweak doc builder instructions Ignore-this: 2bb19a07e3d9c2affe262c65775c5b0c M ./docs/create-doc-builder-vm.txt -1 +1

1 0

patch applied (hackage-server): "Improve create-doc-builder-vm.txt" and 2 others
by devnull＠community.haskell.org 16 Aug '12

16 Aug '12

Thu Aug 16 20:15:51 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Improve create-doc-builder-vm.txt Ignore-this: 9367cdf3bd7b5b8a6bd92677fce802d8 M ./docs/create-doc-builder-vm.txt -9 +60 Thu Aug 16 20:24:42 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Make the 'minimal' Cabal flag 'manual' Ignore-this: 9f6a62a6c7b8dbd2b8a86fe0bc0538ec I think that the intention was that the minimal mode be manually enabled. M ./hackage-server.cabal +1 Thu Aug 16 20:51:48 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Add Cabal flags so that we can control building of individual executables Ignore-this: 799aade064398b94f9e09dafe399831d M ./hackage-server.cabal +18

1 0

[Hackage] #777: cabal install {hledger, others} ExitFailure 11
by Hackage 14 Aug '12

14 Aug '12

#777: cabal install {hledger, others} ExitFailure 11 ---------------------------------+------------------------------------------ Reporter: philips | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.8 Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: ExitFailure Difficulty: unknown | Ghcversion: Platform: Linux | ---------------------------------+------------------------------------------ I am getting ExitFailure 11 when trying to install hledger on Debian and openSUSE. I reported this to the hledger author, Simon, and he said he is experiencing this on his machines too and for other packages, not just hledger. Log file attached. Summary below: {{{ ledger:~/ $ cabal install -v3 hledger Lots of debug output (see attached)... hledger-0.13 failed during the configure step. The exception was: ExitFailure 11 ledger:~/ $ cabal --version cabal-install version 0.8.2 using version 1.8.0.2 of the Cabal library ledger:~/ $ ghc --version The Glorious Glasgow Haskell Compilation System, version 6.12.1 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/777> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 11

patch applied (hackage-server): "Turn namesCache into a CacheableAction" and 3 others
by devnull＠community.haskell.org 05 Aug '12

05 Aug '12

Sat Aug 4 23:12:43 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Turn namesCache into a CacheableAction Ignore-this: 8901de48a19600c986ebca7d3f8720 M ./Distribution/Server/Features/Html.hs -6 +6 Sat Aug 4 23:19:13 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Make recents a CacheableAction Ignore-this: a812652d81d4dc90629907548a4ec17b M ./Distribution/Server/Features.hs -1 +1 M ./Distribution/Server/Features/Packages.hs -9 +10 Sun Aug 5 01:34:59 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Don't store all the blobs in the same directory Ignore-this: 79b6e89b0d3f791823a75b5ca85a3a8 We already have >45k files, and some filesystems don't scale well. M ./Distribution/Server/Framework/BlobStorage.hs -5 +17 Sun Aug 5 01:39:43 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Don't create the blobs directory ourself in bulkImport Ignore-this: 2948ffb8f72308aef4f3753de5d4948c It'll now go wrong, as we don't also create the necessary subdirectories. M ./Distribution/Server.hs -2 +2 M ./Main.hs -1 +1

1 0

patch applied (hackage-server): "Add a CacheableAction type, and use it for the index page" and 5 others
by devnull＠community.haskell.org 04 Aug '12

04 Aug '12

Fri Aug 3 23:42:13 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Add a CacheableAction type, and use it for the index page Ignore-this: 84ef37b4f33f0d875a9380873e9dd07b M ./Distribution/Server/Features/Html.hs -10 +10 M ./Distribution/Server/Framework/Cache.hs -1 +53 M ./Distribution/Server/Util/AsyncVar.hs +2 Sat Aug 4 00:13:07 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Enable CacheableActions to be disabled Ignore-this: 9d0fed17a888e3b94f8aefb16d8f7bcd When they are disabled, any requests for them actually compute the value. This is normally much less efficient, but * when running tests, it makes the test result more consistent, as there's no possibility of an out-of-date cache * When making a Hackage mirror, it means we don't keep regenerating the index page cache M ./Distribution/Server.hs -3 +3 M ./Distribution/Server/Features.hs -3 +3 M ./Distribution/Server/Features/Html.hs -3 +5 M ./Distribution/Server/Framework/Cache.hs -13 +17 M ./Main.hs -12 +19 Sat Aug 4 00:17:28 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Disable caches when running the HighLevelTest Ignore-this: c2b561b8c4cd5fe6ea7d16fc90e601bc M ./tests/HighLevelTest.hs -1 +1 Sat Aug 4 00:35:05 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Bugfix Ignore-this: 7480fa2b2cab01e9ccfd42e6e4e8cd60 M ./Distribution/Server/Features/Html.hs -1 +1 Sat Aug 4 01:15:48 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Make the indextar a CacheableAction too Ignore-this: 2b8904d1d11e74099426d9e265dd51f7 M ./Distribution/Server/Features.hs -1 +1 M ./Distribution/Server/Features/Core.hs -9 +7 Sat Aug 4 02:31:41 BST 2012 Ian Lynagh <ian(a)well-typed.com> * Disable the reverse index for now Ignore-this: 3e6d29f45bac370653f8c127a7f68d94 It has some performance problems M ./Distribution/Server/Acid.hs -11 +13 M ./Distribution/Server/Features.hs -4 +6 M ./Distribution/Server/Features/Html.hs -12 +25 M ./Distribution/Server/Features/PackageList.hs -9 +19 M ./hackage-server.cabal -3 +3

1 0

integrated testing using type "detailed" and test-framework
by Malthe Borch 04 Aug '12

04 Aug '12

What glue is necessary to use the "detailed-0.9" test-suite type with the test-framework (and its HUnit-integration)? I have tried to find documentation online, but much of it seems somewhat outdated or relatively obscure. Ideally, I'd like to follow the guide: $ cabal configure --enable-tests $ cabal build $ cabal test But there seems to be an interface issue between these different test frameworks. \malthe

2 1