Bug 870946 - upgrade to Clementine 1.1
Summary: upgrade to Clementine 1.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: clementine
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jørn Lomax
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-29 09:04 UTC by Marcus Moeller
Modified: 2013-03-08 00:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-08 00:02:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Marcus Moeller 2012-10-29 09:04:57 UTC 
Description of problem:
Clementine 1.1 has been released recently. It would be great if you could update the package accordingly.
Comment 1 Jørn Lomax 2012-10-29 09:18:11 UTC 
I'll try to push it out in the next couple of days. Thanks for informing me :)
Comment 2 Edouard Bourguignon 2013-01-21 13:12:20 UTC 
any news?
Comment 3 Tim Sullivan 2013-01-26 06:20:58 UTC 
I'm also interested in this package being updated. Cheers.
Comment 4 Fedora Update System 2013-02-24 19:51:03 UTC 
clementine-1.1.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/clementine-1.1.1-1.fc18
Comment 5 Fedora Update System 2013-02-26 02:42:31 UTC 
Package clementine-1.1.1-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 clementine-1.1.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-3039/clementine-1.1.1-1.fc18
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2013-03-08 00:02:57 UTC 
clementine-1.1.1-1.fc18 has been pushed to the Fedora 18 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.