Bug 550787 - fbreader is old
Summary: fbreader is old
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fbreader
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL: http://fbreader.org/
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-27 11:48 UTC by DennyHalim.com
Modified: 2010-02-18 22:39 UTC (History)
1 user (show)

Fixed In Version: fbreader-0.12.1-1.fc11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-18 22:27:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description DennyHalim.com 2009-12-27 11:48:43 UTC
rawhide version is 10.7
the latest version is now 12.1

Comment 1 Fedora Update System 2010-01-28 01:00:11 UTC
fbreader-0.12.1-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update fbreader'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1165

Comment 2 Fedora Update System 2010-01-28 01:01:55 UTC
fbreader-0.12.1-1.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update fbreader'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1166

Comment 3 Fedora Update System 2010-02-18 22:27:32 UTC
fbreader-0.12.1-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2010-02-18 22:39:31 UTC
fbreader-0.12.1-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.


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