Bug 827780 - [RFE] update lxapparence to version 0.5.2
Summary: [RFE] update lxapparence to version 0.5.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lxappearance
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-03 01:46 UTC by lyann
Modified: 2012-06-20 00:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-20 00:24:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lyann 2012-06-03 01:46:39 UTC
Description of problem:

There is a new version of lxapparence see here : http://blog.lxde.org/?p=922

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:

Update to the new version

Additional info:

Comment 1 Christoph Wickert 2012-06-03 16:12:57 UTC
This is not a "Review Request" but a "Request for enhancement" (or short RFE). Adjusting summary.

Comment 2 Fedora Update System 2012-06-04 00:08:15 UTC
lxappearance-0.5.2-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/lxappearance-0.5.2-1.fc17

Comment 3 Fedora Update System 2012-06-05 23:09:01 UTC
Package lxappearance-0.5.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 lxappearance-0.5.2-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-8878/lxappearance-0.5.2-1.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-06-20 00:24:44 UTC
lxappearance-0.5.2-1.fc17 has been pushed to the Fedora 17 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.