August 2012 - Libraries

Re: List-0.4.3 (and hexpat)
by Christian Maeder 16 Aug '12

16 Aug '12

Thanks for your prompt response and action! Am 15.08.2012 23:46, schrieb Yair Chuchem: > Hi Christian, > > Please try again now (after a cabal update). > I uploaded List-0.4.4 which removes mapMaybe, and then also uploaded > List-0.5.0 which re-adds it. > hexpat should now be using List-0.4.4 as it wants List < 0.5 > > I'll follow up with a few steps: > * Make myself a rule to test installing hexpat before I push updates to > List in future. > * Contact Stephen to change hexpat to not use unqualified open imports, > at least for List. His email was not in the package description. Christian > * Add docs to my package warning users that using it with unqualified > open imports may be more dangerous than usual (btw unqualified open > imports are always dangerous) because List exports functions which > generalize Prelude functions and shares their names by design. Similar > to how Control.Category exports "." and "id". > > Cheers & Happy coding, > Yair

1 0

List-0.4.3
by Christian Maeder 15 Aug '12

15 Aug '12

Hi, The change in package List-0.4.3 cause hexpat to fail. (It works with List-0.4.2 without "mapMaybe") C. Resolving dependencies... Downloading hexpat-0.20.2... Configuring hexpat-0.20.2... Building hexpat-0.20.2... Preprocessing library hexpat-0.20.2... [ 1 of 12] Compiling Text.XML.Expat.Internal.IO ( Text/XML/Expat/Internal/IO.hs, dist/build/Text/XML/Expat/Internal/IO.o ) [ 2 of 12] Compiling Text.XML.Expat.SAX ( Text/XML/Expat/SAX.hs, dist/build/Text/XML/Expat/SAX.o ) [ 3 of 12] Compiling Text.XML.Expat.Internal.NodeClass ( Text/XML/Expat/Internal/NodeClass.hs, dist/build/Text/XML/Expat/Internal/NodeClass.o ) [ 4 of 12] Compiling Text.XML.Expat.Internal.Qualified ( Text/XML/Expat/Internal/Qualified.hs, dist/build/Text/XML/Expat/Internal/Qualified.o ) [ 5 of 12] Compiling Text.XML.Expat.Internal.Namespaced ( Text/XML/Expat/Internal/Namespaced.hs, dist/build/Text/XML/Expat/Internal/Namespaced.o ) [ 6 of 12] Compiling Text.XML.Expat.Tree ( Text/XML/Expat/Tree.hs, dist/build/Text/XML/Expat/Tree.o ) [ 7 of 12] Compiling Text.XML.Expat.Cursor ( Text/XML/Expat/Cursor.hs, dist/build/Text/XML/Expat/Cursor.o ) [ 8 of 12] Compiling Text.XML.Expat.Internal.DocumentClass ( Text/XML/Expat/Internal/DocumentClass.hs, dist/build/Text/XML/Expat/Internal/DocumentClass.o ) [ 9 of 12] Compiling Text.XML.Expat.Extended ( Text/XML/Expat/Extended.hs, dist/build/Text/XML/Expat/Extended.o ) Text/XML/Expat/Extended.hs:372:25: Ambiguous occurrence `mapMaybe' It could refer to either `Data.List.Class.mapMaybe', imported from `Data.List.Class' at Text/XML/Expat/Extended.hs:83:1-22 or `Data.Maybe.mapMaybe', imported from `Data.Maybe' at Text/XML/Expat/Extended.hs:84:1-17 cabal: Error: some packages failed to install: hexpat-0.20.2 failed during the building phase. The exception was: ExitFailure 1

1 0

gearing up for 2012.4.0.0
by Mark Lentczner 14 Aug '12

14 Aug '12

It's that time again.... time to get cooking on another tasty Haskell Platform release! Here's my updated timeline for 2012.4.0.0, target: *November 12th, 2012* - *August 20th, 2012* - Call for proposals for additions and changes - *September 17th, 2012* - Call for proposals ends (no more proposals considered) - *October 1st, 2012* - Proposals decided, Initial version list - *October 15th, 2012* - First candidates - *October 29th, 2012* - Open issues resolved, Second candidates - *November 5th, 2012* - Final release candidates *If you are maintainer of a library in the platform:* Please start thinking about which version of your library should be in the release. If it will require coordination with versions of other libraries in the platform, now is the time to start coordinating. In mid-september, we will need to hear from the maintainers which version should be included: *I will not automatically bump to the latest version on Hackage for this release.* * * *If you are a maintainer of a library that you'd like to be in the platform: * Now is the time to get a clean version on Hackage, and then put together a proposal for the haskell-platform list. Please see the process for Adding Packages <http://trac.haskell.org/haskell-platform/wiki/AddingPackages>. *If you are part of the reviewing process:* Traditionally, proposals have been accompanied by lengthly discussions, often resulting in deep API design confabs. As we are approaching a release, I'd like to ask all to consider making this round more succinct if at all possible. In particular, it would be great if proposals were keyed to specific revisions of a library to be considered. If consensus is that something needs to be changed before inclusion - it would be best if maintainers took that input into account, turned another library version and placed that up for consideration. Please note the schedule: I'm going to hold October 1st firm. *If you are GHC Central: *I couldn't find a timeline for 7.6. Will that have hit a stable release by October 1st, or should we be planning on shipping 7.4.2 (which I think would be fine.) *If you are a packager or builder of HP releases: *Please review the trac ticket list <http://trac.haskell.org/haskell-platform/report/3>. Please edit tickets to reflect reality: Close things that are fixed or won't ever be done. Edit descriptions with more information if you have it. But most importantly, please assign milestones correctly: If you are going to fix something this time - put it in the 2012.4.0.0 milestone. If it is for the future, put it in Blue Sky. - Mark "mzero" Lentczner, Chef de la Release

3 3

Re: Small problem in containers-0.5.0.0 docs
by Johan Tibell 01 Aug '12

01 Aug '12

Fixed. Thanks for the bug report! In the future you can file reports at https://github.com/haskell/containers/issues to make sure I don't forget about them! :) On Wed, Aug 1, 2012 at 6:30 AM, Christoph Breitkopf <chbreitkopf(a)gmail.com> wrote: > Hello, > > the haddoc sources refer to the strict/lazy modules using single quotes, > which does not work, as is is interpreted as a type reference > (.../Data-Map.html#t:Strict). Replacing the single quotes by double quotes > for a module reference fixes this. (I just had the same problem in > IntervalMap). > > I spotted the problem in Data.Map, but it's probably also present in other > modules. > > Regards, > > Chris

1 0