Re: Test for spam

Seems to have worked. Previous messages were indeed marked as suspicious. On Tue, 4 Jun 2019 at 09:03, Simon Peyton Jones via cabal-devel wrote: > > Dear Cabal-devs > > My earlier messages to cabal-devel was flagged as spam by the time it reached > Michael and Carter. (Perhaps others too.) > >

Re: Pure Haskell replacement for a dependency package

Hi, On Fri, 22 Feb 2019 at 12:53, Mikhail Glushenkov wrote: > > If it doesn't result in too much of a slowdown, I think it would make > sense to do this change. I'd recommend making the choice between > ed25519/eccrypto configurable via a flag so that we could compare the &

Re: cabal user questions

Hi, On Tue, 19 Feb 2019, 21:25 rick > I have some cabal user questions. Should I post them here or on Haskell > cafe? Both are fine, but more people subscribe to haskell-cafe, so your question will likely be answered sooner. ___ cabal-devel mailing lis

Re: Pure Haskell replacement for a dependency package

Hi Marcel, On Tue, 19 Feb 2019, 15:43 Marcel Fourné > Hello, > > hackage-security is using the ed25519 package, which in itself is > wrapper library around a C/Assembly implementation. > I have just released a pure Haskell implementation of that (modulo > slightly different API the same signature

Re: Cabal website

Hi, On 17 June 2018 at 18:20, Christopher Allen wrote: > I don't think this is fair to the maintainers of Cabal and the Cabal > website. You can't do work nobody asked for and then get upset if > people are unwilling to adopt and maintain the unasked-for-code. To be fair, Imants contacted me bef

Re: Upgrading Stack to Cabal 2.2

Hi, On 20 February 2018 at 13:47, Michael Snoyman wrote: > Hi all, > > Oleg mentioned to me on Reddit that a 2.2 branch has been cut for Cabal, and > recommended we try to upgrade Stack to it. I'm sharing information here on > that process in case it's useful to others, either as feedback on the

2.2 release branch created

Hi *, I've just created the branch for the 2.2 Cabal/cabal-install release [1]. If everything goes according to plan, the final release will be out approximately in two weeks' time, i.e. around the end of the month. This is a delay of one month compared with the original plan shared in the previou

Re: Gearing up for the 2.2 release

Hi Daniel, On 27 December 2017 at 17:43, Daniel Trstenjak wrote: > Most likely the stability of the pretty printing of a > GenericPackageDescription > isn't considered that important. > > I just wanted to mention that the order of fields in the stanzas changed > from 'Cabal 1.24/2.0' to the curr

Re: Gearing up for the 2.2 release

Hi Oleg, On 27 December 2017 at 17:17, Oleg Grenrus wrote: > I had a good success with completing a lot of parser work around Christmas, > still on my todo list are: > > - rewriting InstalledPackageInfo parser&printer using new (parsec) > framework, which is (soft) prerequisite to > - changing li

Cabal/cabal-install project ideas for Summer of Code 2018

Hi *, As you are probably aware, it is again the time of the year to come up with project proposals for the next year's Summer of Code [1]. I've started a Wiki page for collecting Cabal/cabal-install HSoC 2018 project ideas [2] - please feel free to add new entries, edit existing ones and add/remo

Gearing up for the 2.2 release

Hi *, It is time to start planning for the 2.2 release of Cabal/cabal-install. The original plan was to do it before the end of the year, however, given the current state of HEAD and the fact that GHC 8.4 is going to be released in February, I think it won't be a tragedy if we delay 2.2 a little.

[ANN] Cabal 2.0.1.1/cabal-install 2.0.0.1 released

Hi *, Cabal 2.0.1.1 and cabal-install 2.0.0.1 are now available from Hackage and the download page: http://hackage.haskell.org/package/Cabal-2.0.1.1 http://hackage.haskell.org/package/cabal-install-2.0.0.1 https://www.haskell.org/cabal/download.html Changes in this release: Cabal 2.0.1.1:

Re: new cabal install binaries

Hi Gershom, On 4 December 2017 at 02:08, Gershom B wrote: > when we build the new platform we're going to have new cabal-install > binaries for 2.0.1.0. It would be better if we provided the same ones > as provided on the cabal website. Is there anyone lined up to build > any of these, or would y

Re: new cabal install binaries

Hi Gershom, On 4 December 2017 at 02:08, Gershom B wrote: > when we build the new platform we're going to have new cabal-install > binaries for 2.0.1.0. It would be better if we provided the same ones > as provided on the cabal website. Is there anyone lined up to build > any of these, or would y

Re: Summer of Haskell | Cabal Project

Hi, On 6 May 2017 at 19:13, Pranit Bauva wrote: > Hey Mikhail, > > Thanks! I have applied on the Google form. I have also made a google > doc and here[1] is the link. Great! Good luck with your application! ___ cabal-devel mailing list cabal-devel@hask

Re: Summer of Haskell | Cabal Project

Hi Pranit, On 3 May 2017 at 06:20, Pranit Bauva wrote: > Hey everyone, > > I am Pranit Bauva and I am interested in participating in the Summer > of Haskell program to complete the project "Last Mile for `cabal > new-build`". I have got a few PRs merged[1] and I am now working on > another one[2]

Re: Misleading home page link

Hi Matthew, On 5 May 2017 at 01:32, Matthew Fernandez wrote: > > [...] > The label > "cabal-install" no longer seems to be used by itself; this search returns no > results. Fixed, thanks! ___ cabal-devel mailing list cabal-devel@haskell.org http://mail

Re: Cabal at BayHac 2017

Hi Kristen, On 12 February 2017 at 20:25, Kristen Kozak wrote: > Hello, > > I am considering volunteering at BayHac to help people hack on Cabal, > though I don't know enough of the codebase to do it myself. Is anyone > else interested in helping? BayHac is April 7th through 9th in San > Franci

2.0 branch created

Hi *, Just a heads-up that the 2.0 release branch for Cabal/cabal-install has been created. If everything goes as planned, I'll tag the releases next week, so please hurry up if you want your patches to be included in this version. List of issues I want to see resolved before the release: https:

Re: cabal release binaries for 1.24.0.2 ?

Hi, On 11 January 2017 at 18:37, Gershom B wrote: > It seems like the binaries (aside from the os x one) aren't up yet. It > would be good to have them for the new ghc and platform. Now they are. Sorry for dragging my feet on that. ___ cabal-devel mail

Re: cabal release binaries for 1.24.0.2 ?

Hi, On 7 January 2017 at 21:02, Gershom B wrote: > I noticed that there there are no binaries for 1.24.0.2 I'll build them tomorrow. BTW, can you please send me an OS X binary for 1.24.0.2? > the webpage still links the source tarball for 1.24.0.1 as the latest? Fixed.

[ANN] Cabal-1.24.2.0 and cabal-install-1.24.0.2 have been released

Hi *, Cabal 1.24.2.0 and cabal-install 1.24.2.0 are now available from Hackage and the download page: http://hackage.haskell.org/package/Cabal-1.24.2.0 http://hackage.haskell.org/package/cabal-install-1.24.0.2 https://www.haskell.org/cabal/download.html Binaries for cabal-install will be uploade

Re: GHC 8.0.2 status

Hi, On 10 October 2016 at 18:12, Edward Z. Yang wrote: > If we want a bugfix version of Cabal in with GHC 8.0.2 this is our last > chance. I'll try to fix the backwards compat issue with https://github.com/haskell/cabal/pull/3955 ASAP so that we can get 1.24.1.0 out of the door.

Hackathon 2016 Wiki page

Hi *, I started writing a Wiki page with a list of ideas for this weekend's HaskellX hackathon in London. Please feel free to expand and improve: https://github.com/haskell/cabal/wiki/Hackathon-2016 ___ cabal-devel mailing list cabal-devel@haskell.org h

Re: cabal new-* commands awesomeness

Hi, On 19 September 2016 at 08:46, Ramakrishnan Muthukrishnan wrote: > 1. Will the `new' variants become the default? That will be nice! Yes, that's the plan. This won't happen in the next release (2.0), though. > 2. I would like to contribute to Cabal project (especially after the > recent "di

Re: Opening up Cabal development

On 14 July 2016 at 03:13, Edward Z. Yang wrote: >1. Can we parse all of Hackage? > >[...] > >3. Can we build all Setup.hs scripts on Hackage? This lets us know > which APIs in Cabal matter, and which ones we can change. > We'll need to establish base truth for this. If so

Re: Opening up Cabal development

Hi, On 14 July 2016 at 01:32, Edward Z. Yang wrote: > Why don't we give them all commit access! (If we want to do (1) also > look at the current PR queue.) Fine with me. I tried something like this on a smaller scale previously, giving write access to a number of people with a history of qualit

Re: I reorged labels on Cabal's GitHub

Hi, On 12 July 2016 at 23:58, Edward Z. Yang wrote: > For the PR, we can put in a checklist: > > [ ] If you made a BC-breaking change, did you add an entry to the > changelog? > [ ] If you added a new user-level feature, did you add an entry > to the changelog? Did you write docs for it?

Re: I reorged labels on Cabal's GitHub

Hi, On 12 July 2016 at 13:03, Oleg Grenrus wrote: > Looks good indeed! > > I have few questions: > - what is purpose of `paging:*` labels, to help people see issues they are > interested in? How it’s different from assignees (which can be multiple)? "Assignee" usually means that the implementati

Re: I reorged labels on Cabal's GitHub

Hi, On 11 July 2016 at 06:37, Edward Z. Yang wrote: > If you hate it I can change it back but give it a try for now. > If the "component" prefix in "component: solver" is too long we could go for > something like "C-solver" but I think that is less transparent. Thanks, looks much better than the

Re: [Haskell-cafe] [Haskell] The Haddock documentation is not showing up on the Hackage

Hi, > On Mon, Jun 27, 2016 at 4:01 PM, Henning Thielemann > wrote: >> Here is a script that should help creating the docs locally and upload >> them to Hackage: >> >> https://raw.githubusercontent.com/ekmett/lens/master/scripts/hackage-docs.sh Note that starting with cabal-install 1.24 you can u

Wanted: cabal-install 1.24.0.0 binary for OS X

Hi *, I've uploaded cabal-install 1.24.0.0 binaries for Linux and Windows (both i386 and x86-64) to https://www.haskell.org/cabal/download.html. I'd also like to upload an OS X binary, but I don't have access to an OS X machine currently. Can someone please build an OS X binary for cabal-install 1

Cabal 1.24 status update

Hi *, A short update on the status of the 1.24 release. Due to GHC 8 final having been repeatedly postponed we were able to get the nix-local-build work and a bunch of other patches initially targeted for 1.24.1.0 merged before the first release off the 1.24 branch. However, a number of solver i

Re: Running the Cabal tests

Hi, On 19 March 2016 at 08:35, Erik de Castro Lopo wrote: > Hi all, > > I hacked together what I thought was a neat little feature (a 3 line diff) > and thought I'd add a test. Thats when I figured out I couldn't even run > the tests. > > Reading `Cabal/tests/Readme.md` I see I need to set the en

Cabal 1.24 and 1.26 status update

Hi *, A short update on the current status of the 1.24 branch and plans for the future. Given that the GHC 8 final release is fast approaching, I've decided to create the 1.24 branch before the GHC 8 RC3 has been released. This means that some of the Cabal features initially planned for 1.24 (see

Cabal 1.24 branch created

Hi *, I've just created the 1.24 branch. I've also uploaded release candidates of Cabal and cabal-install 1.24 to Hackage: http://hackage.haskell.org/package/Cabal-1.24.0.0/candidate/Cabal-1.24.0.0.tar.gz http://hackage.haskell.org/package/cabal-install-1.24.0.0/candidate/cabal-install-1.24.0.0.t

Cabal 1.24 status update

Hi *, Just a short update on the status of the 1.24 release. Since the GHC 8 release has been delayed somewhat, I've postponed creating the 1.24 branch. Will do that either before GHC 8 RC3 release or GHC 8 final (if there won't be a GHC 8 RC3). Here's the list of remaining unmerged PRs that I pl

Re: [Haskell-cafe] Doc generation?

Hi, On 20 January 2016 at 09:49, Sven Panne wrote: > 2016-01-20 8:35 GMT+01:00 Mikhail Glushenkov : >> >> You're welcome to open a ticket on the hackage-server bug tracker. > > > I've reported this several times through several channels Those tickets are abou

Re: [Haskell-cafe] Doc generation?

Hi, On 20 January 2016 at 08:09, Sven Panne wrote: > Are there any safeguards on the Hackage server side to guarantee consistency > between the uploaded package and the uploaded docs? (i.e. make sure it's the > right version etc.) Are there checks on the server side that the > cross-package links

Re: [Haskell-cafe] Doc generation?

Hi *, On 19 January 2016 at 23:37, Noon Silk wrote: > Thanks Mark and All, > > Indeed, I've been generating the docs myself offline; I didn't know about > looking for the docs on stackage; thanks! Note that with the Git version of cabal-install you can run 'cabal upload --doc' to upload the do

Re: Cabal status for GHC 8.0.1

Hi, On 12 January 2016 at 17:50, Ben Gamari wrote: > Within what timeframe in particular do you think we'll > be able to have a release tagged and (and ideally released)? Is late > January possible? Yes, I think it should be possible. In fact, all Cabal library changes required by nix-local-buil

Re: Release planning?

Hi Simon, On 14 December 2015 at 14:03, Simon Peyton Jones wrote: > | Yes, there will be a release of Cabal/cabal-install together with GHC > | 8. > > Can I ask what will be in it? Specifically, I would love to know > what you plan concerning the issues in this snip: I've just posted a status

Cabal/cabal-install 1.24 release status

Hi *, As some of you know, I've recently been elected as Cabal "chair"/release coordinator. GHC 8/Cabal 1.24 release date is fast approaching, so I'll try to summarise my current plans regarding the next release. Release schedule: * I'll create the 1.24 branch in about two weeks' time (Dec. 30

Re: Release planning?

Hi, On 13 December 2015 at 21:01, Echo Nolan wrote: > Is it the general rule that Cabal releases are synced with GHC releases, or > can Cabal releases be more frequent? Yes, they can, and we actually want them to. Ideally, a new Cabal/cabal-install version would be released every six months, tho

Re: Release planning?

Hi, On 13 December 2015 at 14:05, Bardur Arantsson wrote: > Hi all, > > Where does release planning happen? I'd like to start on merging some > solver-related PRs, but if there's an imminent release, that might not > be such a good idea... Yes, there will be a release of Cabal/cabal-install toge

Re: Hints on fixing #2645: Properly merge preferences (dependency resolution)

Hi, On 28 November 2015 at 10:59, Martin Vlk wrote: > Oh, and a primer on the overall cabal design would be also very useful! Take a look at https://github.com/haskell/cabal/wiki/Source-Guide ___ cabal-devel mailing list cabal-devel@haskell.org http://

Re: [Freebsd-haskell] Cabal segfaults after update to GHC-7.10.2 from ports

Hi, On 20 October 2015 at 13:36, Eric McCorkle wrote: > More info on this... It seems to be an LLVM issue. Blowing everything away > and rebuilding everything without LLVM fixes the issue. Too bad though, > LLVM worked just fine on FreeBSD through 7.8.3. You may want to report this on the GHC

Re: IRC logs for #hackage

Hi, On 14 October 2015 at 09:02, Danny Navarro wrote: > I was about to send a PR [1] to Chris' Done http://ircbrowse.net/, but > I'd rather have explicit permission before doing so. I'm not sure who > should I'm ask for though. I don't think anyone will object, the channel is public anyway.

Re: Global Constraints for Cabal and also Release Plan?

Hi Gershom, On 22 September 2015 at 00:11, Gershom B wrote: > Any more feedback on this? And also, do we have any plans for an > upcoming Cabal release? Re: next release, I think we should do one in the near future, but I'd like to see some outstanding PRs merged first. I have the following prel

Re: Global Constraints for Cabal and also Release Plan?

On 24 September 2015 at 17:56, Gershom B wrote: > Consider for example if we have a configure build-type, that runs an autoconf > script. It is not enough that the executable we run be in the path, but also > that the “path” available to the autoconf script be amended as well. Yes, 'extra-prog-

Re: Global Constraints for Cabal and also Release Plan?

On 24 September 2015 at 17:06, Gershom B wrote: > So, I want MSys2 tools in my path but _only_ when I am building cabal > packages, and not otherwise. IIUC, 'extra-prog-path' in '~/.cabal/config' already does what you want. It looks like it also supports multiple directories, using comma as sepa

Re: UseSandbox

Hi, On 3 July 2015 at 18:09, Bardur Arantsson wrote: > The checks rely on information which the sub-commands will use (or will > have to look up a second time)... hence I want to store it in UseSandbox :). Yeah, so you can do the check in loadConfigOrSandboxConfig and then put the result of it i

Re: UseSandbox

Hi, On 3 July 2015 at 16:47, Bardur Arantsson wrote: > Well, I'd like to split up the "get all the information we need" bit > from the individual commands. UseSandbox is produced by loadConfigOrSandboxConfig. Perhaps you can move your check there? ___

Re: UseSandbox

Hi, On 3 July 2015 at 06:30, Bardur Arantsson wrote: > Hi all, > > Am I missing something which necessitates using only the FilePath? Adding extra info is absolutely fine, it's just that I never needed it. What do you want to add? ___ cabal-devel maili

Re: Making cabal-install SSL capable

Hi, On 18 May 2015 at 20:22, Gershom B wrote: > So perhaps we can just patch cabal to warn on using wget or powershell > backends that if there are issues they should try one of the fully finished > options, and then we can merge? Sure, please send us a pull request.

Re: What is the error mean for bloomfilter?

On 16 May 2015 at 17:35, Peng Yu wrote: > But I am not able to install version 2.0.1. How to get 2.0.1 via cabal? It hasn't been released yet. You can get a patched version from GitHub: $ git clone https://github.com/mikeizbicki/bloomfilter.git bloomfilter-2.0.1 $ cd bloomfilter-2.0.1 $ cabal in

Re: Why alex can not be automatically installed?

Hi, On 16 May 2015 at 03:55, Peng Yu wrote: > Hi, I see the following error. Why alex can not be automatically installed? See https://github.com/haskell/cabal/issues/220. Patches welcome! ___ cabal-devel mailing list cabal-devel@haskell.org http://mail

Re: What is the error mean for bloomfilter?

Hi, On 16 May 2015 at 03:57, Peng Yu wrote: > Data/BloomFilter/Mutable.hs:136:9: > Non type-variable argument > in the constraint: [...] Not a Cabal issue: the library wasn't updated to work with GHC 7.10. See https://github.com/bos/bloomfilter/issues/11 and https://github.com/bos/bloo

Re: Making cabal-install SSL capable

On 8 May 2015 at 00:14, Gershom B wrote: > On my branch now, everything "should" work: > https://github.com/gbaz/Cabal/tree/https Thanks for working on this. I only had time to take a brief glance, but everything looks good so far. Hope we can merge your patches soon. > (note that even though I

Re: Cabal and simultaneous installations of the same package

On 7 May 2015 at 22:34, Simon Peyton Jones wrote: > Dear Cabal developers > > I guess everyone is busy, but I feel a bit stuck on knowing how to make > progress on this thread. Vishal Agrawal's GSoC proposal has been accepted. I guess we'll have to wait and see what comes out of it now. _

Re: Making cabal-install SSL capable

Hi, On 6 May 2015 at 20:08, Thomas Tuegel wrote: > The saved program configuration is not serialized in > `dist/setup-config`, [1] so it must be regenerated at runtime every > time, anyway. We don't want to configure all known built-in programs on each 'cabal upload', though, so we should introd

Re: Making cabal-install SSL capable

On 6 May 2015 at 17:43, Gershom B wrote: > I’m less certain about the use of ProgramDB — the documentation suggests it > will only be populated from command line flags in the “configure” step, or > from .cabal files. Since upload/download do not take place in such settings, > I don’t think it w

Re: Making cabal-install SSL capable

On 6 May 2015 at 00:26, Gershom B wrote: > Ok, on my "https" branch here: https://github.com/gbaz/Cabal/tree/https Looks like a good first step. Consider using machinery in Distribution.Simple.Program.Db for searching for curl/wget in path or in user-provided location. I'd also use something lik

Re: Making cabal-install SSL capable

Hi, On 4 May 2015 at 08:31, Michael Snoyman wrote: > Just a little update on this. I pinged the author of publicsuffixlist > (necessary for proper cookie domain handling) about removing the > data-default dependency, and after discussion we decided to just merge the > code into http-client instea

Re: How to install cabal after building ghc from source

Hi, On 26 April 2015 at 04:26, Peng Yu wrote: > I get the following error. How to fix it? Try 'EXTRA_CONFIGURE_OPTS="" ./bootstrap.sh' . ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel

Re: How to install cabal after building ghc from source

Hi, On 26 April 2015 at 04:12, Peng Yu wrote: > Hi, I following the following instructions to install ghc from source. > Could anybody let me know what is the appropriate step to install > cabal? Thanks. Try the bootstrap.sh script [1]. [1] https://github.com/haskell/cabal/blob/master/cabal-ins

Re: Cabal and cabal-install minor release (1.22.2.0)

Hi, On 22 March 2015 at 00:49, Miëtek Bak wrote: > Thanks, Ryan. > > > Binaries of cabal-install 1.22.2.0 are now available in Halcyon on the > following platforms: > > [...] That's quite impressive! Have you considered adding Windows support? Our release process could use some automation in th

Re: Cabal and cabal-install minor release (1.22.2.0)

Hi, On 21 March 2015 at 22:34, Ryan Thomas wrote: > There are a couple of outstanding items to tie off with this release: > - The Windows/OSX/Linux specific binaries need to be built and updated > on the download page; Johan I will probably need some guidance on the > process for this. I can bui

Re: Ryan Thomas is the new release manager

Welcome onboard Ryan! On 21 March 2015 at 10:17, Johan Tibell wrote: > Hi everyone, > > I haven't had the time recently to give cabal release process the it > deserves, so I'm happy to announce that Ryan Thomas (CCed) has agreed to > take over the release manager responsibility. > > [...] ___

Re: Please review: new wiki page with release instructions

Hi, On 19 March 2015 at 17:47, Herbert Valerio Riedel wrote: > done (and it still validates): > > > http://git.haskell.org/ghc.git/commitdiff/7c132c02436fadaa70674bbfe38b21a67c4fed3a Great, thanks! ___ cabal-devel mailing list cabal-devel@haskell.or

Re: Please review: new wiki page with release instructions

Hi, On 17 March 2015 at 21:43, Johan Tibell wrote: > If someone could let me know when all the needed patches are on the 1.22 > branch (and if we need both a Cabal and cabal-install release), I will make > the release and take it as an opportunity to validate the release process > instructions.

Re: Cabal webpage on haskell.org

Hi, On 18 March 2015 at 22:55, Gershom B wrote: > Mitek: Go ahead and send on a public ssh key to admin@ and we'll get > you access to that portion of the site. A better idea is to upload the website's source files to GitHub and let people send us pull requests there. I can do that if someone gi

Re: Please review: new wiki page with release instructions

Hi, On 17 March 2015 at 16:15, Thomas Tuegel wrote: > > Otherwise, please alert me if you have any blocking > issues; AFAIK there are none at this time. There are two test cases that are failing with 7.10, but fixing them will probably only require changes to the tests themselves. I'm looking in

Re: Please review: new wiki page with release instructions

Hi Johan, On 16 March 2015 at 08:14, Johan Tibell wrote: > [...] > > https://github.com/haskell/cabal/wiki/Making-a-release Looks OK, thanks for doing this. ___ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/li

Re: Looking for a new release manager for cabal

Hi, On 22 February 2015 at 14:01, Johan Tibell wrote: > > Hi, > > After about 3 years of cabal releases I'm looking for someone else to take > over the responsibility as cabal release manager. Thank you for all your hard work managing Cabal releases during all this time.

Re: Call for 1.22 binaries

Hi, On 5 January 2015 at 16:48, Johan Tibell wrote: > > Linux, Windows, and OS X binaries uploaded. BTW, if we're going to compress the Windows binary, it's better to use .zip since Windows doesn't support .tar.gz by default. ___ cabal-devel mailing li

Re: Call for 1.22 binaries

​​Hi, On 5 January 2015 at 00:26, Johan Tibell wrote: > Hi, > > As per usual I need help building binaries (to put on haskell.org) for the > release. In particular I need binaries for Windows and Linux. And here's the Windows binary. ​ cabal-1.22.0.0-i386-unknown-mingw32.exe

Re: Call for 1.22 binaries

Hi, On 5 January 2015 at 00:26, Johan Tibell wrote: > Hi, > > As per usual I need help building binaries (to put on haskell.org) for the > release. In particular I need binaries for Windows and Linux. Attaching the Linux binary.​ cabal-1.22.0.0-i386-unknown-linux.tar.gz

Re: Cabal 1.22 RC ready to test

Hi, On 3 January 2015 at 03:36, Johan Tibell wrote: > If I don't hear anything the next few days I will make the release. The test suite doesn't compile with GHC HEAD on Travis. ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.or

Re: Please test: release candidates for Cabal/cabal-install patch releases on the 1.18 and 1.20 branches

Hi, On 13 December 2014 at 16:12, Johan Tibell wrote: > I can include it in the release but I rather not make another RC, it takes > an hour or so. Could you please test on your machine that the extra fix > works as intended? Thanks! I did verify it on my machine previously. It does pass on Trav

Re: Please test: release candidates for Cabal/cabal-install patch releases on the 1.18 and 1.20 branches

Hi Johan, I pushed a very minor fix to 1.18/1.20. Would be nice to have it included in the release. ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel

Re: Linker change in GHC 7.8 leads to widespread issues

Hi, On 4 December 2014 at 17:50, Joachim Breitner wrote: > > in this case, can we get a fixed Cabal in 7.8.4? This is up to whoever manages the release at GHC HQ, which I guess means Austin. ___ cabal-devel mailing list cabal-devel@haskell.org http://w

Re: Linker change in GHC 7.8 leads to widespread issues

Hi, On 4 December 2014 at 09:45, Joachim Breitner wrote: > is the bug in Cabal or cabal-install? It's in Cabal. So once the new point releases are out, the users will need to run `cabal install cabal-install --constraint="Cabal > 1.20.0.2"`. ___ cabal-

Re: Linker change in GHC 7.8 leads to widespread issues

Hi, On 4 December 2014 at 00:44, Bryan O'Sullivan wrote: > Thanks, Mikhail! Does this imply that package authors can simply advise bug > reporters to upgrade cabal-install? Yes, once the new point releases of Cabal/cabal-install are out (in a week or two, according to Johan). ___

Re: Ready to make release candidates for 1.18 and 1.20 bugfix releases

Hi, On 3 December 2014 at 18:04, Mikhail Glushenkov wrote: > We probably also want to include a fix for > https://github.com/haskell/cabal/issues/2207 > I'll write a patch unless someone beats me to it. This is now fixed both in HEAD an

Re: Linker change in GHC 7.8 leads to widespread issues

Hi, On 2 December 2014 at 22:06, Bryan O'Sullivan wrote: > Hi folks, > > It seems that something somewhere in linker-land changed in GHC 7.8 such > that packages that include C components now need to be built with > position-independent code on some platforms. I've now fixed this issue in Cabal

Re: Ready to make release candidates for 1.18 and 1.20 bugfix releases

Hi, On 3 December 2014 at 17:51, Johan Tibell wrote: > Hi! > > I believe I have merged all the fixes people wanted to see in 1.18 and 1.20. We probably also want to include a fix for https://github.com/haskell/cabal/issues/2207 I'll write a patch unless someone beats me to it. __

Re: feedback for changes to the commandline documentation/help, please

Hi, On 18 November 2014 00:31, lennart spitzner wrote: > https://gist.github.com/lspitzner/36321a9f074cb9b897ac Looks good after a cursory review. Regarding your questions: > does cabal freeze really overwrite any existing cabal.config? Not sure (I don't use 'freeze' much). You can always tes

Re: Where to put these flags?

Hi, On 2 November 2014 12:26, Sven Heyll wrote: > a) extend global flags? > b) extend only ConfigExFlags? > (which means users cannot cross-compile without explicitly calling > 'configure', OTOH users can set these values in cabal config file) > c) continue to add a set of flags to eve

Re: improving commandline documentation/help

Hi, On 30 October 2014 16:22, lennart spitzner wrote: > hello cabal devs, > > i am willing to put a bit of time into improving the help texts of > cabal-install. some questions: > > 1) nobody else is working on this, right? is there risk that it > interferes with other's work? (i'd basically touc

Re: New fields/flags and semantics for GHCJS

Hi, On 28 October 2014 21:00, Luite Stegeman wrote: > Hi all, > > I've been maintaining a Cabal fork for GHCJS. The GHCJS-specific bits have > been relatively stable for a while now, and are feature complete, apart from > a few small features that I'll complete later this week. > > So I think it'

Re: tweaks to cabal-install bootstrap.sh

Hi, On 28 September 2014 17:14, Jake Wheat wrote: > [...] > Is it possible to put these changes into the main cabal repo? Sure, please send us a pull request. ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/

Re: add an x86_64 linux build for cabal-install on the binaries site?

Hi, On 23 September 2014 05:47, Carter Schonwald wrote: > Hey All, > http://www.haskell.org/cabal/download.html > current lacks an x86_64 linux build, and while most linux distros DO provide > a relatively recent cabal-install, might be good to make that available, it > is one of the most widely

Re: HEADS UP: Running cabal install with the latest GHC

Hi, On 13 August 2014 16:22, Mikhail Glushenkov wrote: > End of the year, I think. Correction: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.10.1 says "February 2015". ___ cabal-devel mailing list cabal-devel@haskell.org http://ww

Re: HEADS UP: Running cabal install with the latest GHC

Hi, On 13 August 2014 16:12, Johan Tibell wrote: > I'm still aiming for another > major release before 7.10? When's 7.10 scheduled before? End of the year, I think. ___ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/lis

Re: Fw: cabal-install-latest is not pointing to latest release

Hi, On 29 July 2014 09:44, Johan Tibell wrote: > > Uploaded, thanks! I've also built the (32-bit) Linux binary. ​ cabal-1.20.0.3-i386-unknown-linux.tar.gz ​ ___ cabal-de

Re: Fw: cabal-install-latest is not pointing to latest release

Hi, On 24 July 2014 11:41, Johan Tibell wrote: > Hi, > > We don't have any binary builds of 1.20.0.3 so I thought it better to > point to a release where we have such. If someone can provide me with > a windows build (.tar.gz containing exe please, built using latest > Cabal-1.20. Include the arc

Re: Killing or resurrecting version tags for good

Hi, On 26 July 2014 23:36, Edward Z. Yang wrote: > Hello all, > > A while back, I was nattering around the parsing code for Cabal, > and I noticed that Cabal still had code for parsing version tags, > but was explicitly *not* printing out version tags. [...] > > So if we're keeping tags around, a

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

Hi, On 26 July 2014 08:55, Nikita Karetnikov wrote: > > What version of network is it? I ran ‘grep -r “host lookup failure”’ on > the source of 2.5.0.0 and didn’t find anything. $ cabal sandbox hc-pkg list | grep network network-2.5.0.0 It probably uses perror or something like it. ___

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

Hi, On 26 July 2014 00:20, Nikita Karetnikov 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 update Downloading t

  1   2   >