Bug 879774

Summary: Lazarus 1.0.2 is available
Product: [Fedora] Fedora Reporter: Heiko Adams <bugzilla>
Component: lazarusAssignee: Joost van der Sluis <joost>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: joost, mattia.verga, noelduffy, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-12 15:22:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Heiko Adams 2012-11-24 09:32:20 UTC
Currently fedora provides version 0.9.30.4 upstream has recently released version 1.0.2.

It would be nice if fedora bits could be updated to the current version

Comment 1 Noel Duffy 2013-01-03 08:24:18 UTC
Per this comment thread on reddit:

http://www.reddit.com/r/linux/comments/15tzau/what_should_fedora_do_in_2013/c7pxm8r

And with his permission, adding T Callaway to the cc list.

Comment 2 Fedora Update System 2013-01-03 18:04:28 UTC
lazarus-1.0.4-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/lazarus-1.0.4-1.fc18

Comment 3 Fedora Update System 2013-01-03 23:47:12 UTC
Package lazarus-1.0.4-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lazarus-1.0.4-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-0133/lazarus-1.0.4-1.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-01-12 15:22:03 UTC
lazarus-1.0.4-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.