Bug 841921 - Update to sx-2.11
Summary: Update to sx-2.11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sx
Version: rawhide
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Pierguido Lambri
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 841922
TreeView+ depends on / blocked
 
Reported: 2012-07-20 14:39 UTC by Niels de Vos
Modified: 2012-08-09 23:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 841922 (view as bug list)
Environment:
Last Closed: 2012-08-09 22:49:27 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Niels de Vos 2012-07-20 14:39:56 UTC 
sx-2.11 has been made available, please update the Fedora packages to this new version.
Comment 1 Fedora Update System 2012-07-27 13:26:38 UTC 
sx-2.11-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/sx-2.11-1.fc16
Comment 2 Fedora Update System 2012-07-27 13:26:47 UTC 
sx-2.11-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/sx-2.11-1.fc17
Comment 3 Fedora Update System 2012-07-28 01:21:00 UTC 
Package sx-2.11-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sx-2.11-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-11200/sx-2.11-1.fc16
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2012-08-09 22:49:27 UTC 
sx-2.11-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 5 Fedora Update System 2012-08-09 23:20:56 UTC 
sx-2.11-1.fc16 has been pushed to the Fedora 16 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.