Bug 953799 - python-lamson-1.3.4 is available
Summary: python-lamson-1.3.4 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-lamson
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Praveen Kumar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-19 08:38 UTC by Upstream Release Monitoring
Modified: 2013-05-22 04:13 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-22 04:13:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2013-04-19 08:38:06 UTC
Latest upstream release: 1.3.4
Current version in Fedora Rawhide: 1.1
URL: http://pypi.python.org/packages/source/l/lamson

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 2013-04-21 09:19:20 UTC
python-lamson-1.3.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-lamson-1.3.4-1.fc19

Comment 2 Fedora Update System 2013-04-21 09:28:23 UTC
python-lamson-1.3.4-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/python-lamson-1.3.4-1.fc18

Comment 3 Fedora Update System 2013-04-21 17:39:30 UTC
Package python-lamson-1.3.4-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-lamson-1.3.4-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-6192/python-lamson-1.3.4-1.fc19
then log in and leave karma (feedback).


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