Issue 598 in xmonad: Join stackage

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 598 in xmonad: Join stackage

codesite-noreply@google.com
Status: Accepted
Owner: nome... at gmail.com

New issue 598 by nome... at gmail.com: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

Currently, xmonad does not build against the packages in the latest  
Stackage LTS release, in particular utf8-string-1. It would be great if  
xmonad would join stackage so that such problems are detected early. It  
also gives you some QA for free: http://www.stackage.org/authors

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #1 on issue 598 by [hidden email]: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

I just tried bumping the upper bound on the utf8-string dependency to ">=  
0.3 && < 1.1" in xmonad.cabal and it appears to build fine against Stackage  
LTS 2.7. So I believe this is a one-line fix. A grep of the xmonad source  
reveals no use of the deprecated imports that were removed in the bump from  
0.3.x to 1.0, and the same holds for XMonadContrib. I'll submit a patch.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #2 on issue 598 by [hidden email]: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

Awesome, thanks!

Can you also send a pull request to add it to Stackage?
http://www.stackage.org/authors


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #3 on issue 598 by jshholland: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

Created https://github.com/fpco/stackage/pull/584

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #4 on issue 598 by jshholland: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

The pull request has been rejected because my patch to increase the bound  
on utf8-string hasn't made it to a released Hackage version yet. Is there a  
release planned yet? Does this merit a full point release on its own?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #5 on issue 598 by [hidden email]: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

With my Debian packaging maintainer hat on: Yes, it does merit a release,  
either on its own or a proper new release.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #6 on issue 598 by [hidden email]: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

Any plans for a point release with this patch?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad
Reply | Threaded
Open this post in threaded view
|

Re: Issue 598 in xmonad: Join stackage

codesite-noreply@google.com

Comment #7 on issue 598 by [hidden email]: Join stackage
https://code.google.com/p/xmonad/issues/detail?id=598

Bump. Still waiting on that release.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
xmonad mailing list
[hidden email]
http://mail.haskell.org/cgi-bin/mailman/listinfo/xmonad