Bug 821668 - ghc-shakespeare-1.0.0.2 is available
Summary: ghc-shakespeare-1.0.0.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ghc-shakespeare
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-15 10:16 UTC by Upstream Release Monitoring
Modified: 2012-07-30 17:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-18 04:33:26 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-05-15 10:16:51 UTC
Latest upstream release: 1.0.0.2
Current version in Fedora Rawhide: 1.0.0.1
URL: http://hackage.haskell.org/packages/archive/shakespeare/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 2 Fedora Update System 2012-06-28 05:29:42 UTC
ghc-hamlet-1.0.1.3-1.fc17,ghc-shakespeare-1.0.0.2-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ghc-hamlet-1.0.1.3-1.fc17,ghc-shakespeare-1.0.0.2-1.fc17

Comment 3 Fedora Update System 2012-07-10 16:25:13 UTC
ghc-hamlet-1.0.1.3-1.fc17, ghc-shakespeare-1.0.0.2-1.fc17, ghc-hakyll-3.2.7.2-4.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2012-07-15 13:32:17 UTC
ghc-shakespeare-1.0.0.2-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/ghc-shakespeare-1.0.0.2-1.el6

Comment 5 Fedora Update System 2012-07-30 17:28:44 UTC
ghc-shakespeare-1.0.0.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository.


Note You need to log in before you can comment on or make changes to this bug.