Bug 868835 - unlambda-0.1.2 is available
Summary: unlambda-0.1.2 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: unlambda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shakthi Kannan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-22 09:13 UTC by Upstream Release Monitoring
Modified: 2012-11-19 06:15 UTC (History)
2 users (show)

Fixed In Version: unlambda-0.1.2-1.fc17
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-19 06:15:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-10-22 09:13:06 UTC
Latest upstream release: 0.1.2
Current version in Fedora Rawhide: 0.1
URL: http://hackage.haskell.org/package/unlambda

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 1 Fedora Update System 2012-10-27 04:07:56 UTC
unlambda-0.1.2-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/unlambda-0.1.2-1.fc17

Comment 2 Fedora Update System 2012-10-27 04:08:07 UTC
unlambda-0.1.2-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/unlambda-0.1.2-1.fc18

Comment 3 Fedora Update System 2012-10-28 01:00:10 UTC
Package unlambda-0.1.2-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing unlambda-0.1.2-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17054/unlambda-0.1.2-1.fc17
then log in and leave karma (feedback).


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