Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 641923 - Need libindi 0.6.1 for kdeedu 4.5 (f13)
Summary: Need libindi 0.6.1 for kdeedu 4.5 (f13)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libindi
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Sergio Pascual
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 618776
Blocks: kde-4.5
TreeView+ depends on / blocked
 
Reported: 2010-10-11 14:41 UTC by Rex Dieter
Modified: 2010-11-03 21:08 UTC (History)
3 users (show)

Fixed In Version: libindi-0.6.2-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of: 618776
Environment:
Last Closed: 2010-11-03 21:08:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Rex Dieter 2010-10-11 14:41:00 UTC 
+++ This bug was initially created as a clone of Bug #618776 +++

Description of problem:
We currently only have libindi 0.6 in Fedora. We need 0.6.1 to build kdeedu 4.5 against, ASAP in Rawhide, and whenever we'll want to push KDE 4.5 to releases.

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

How reproducible:
Always.

Steps to Reproduce:
1. Try to build kdeedu 4.5 or trunk (4.6).
  
Actual results:
kdeedu refuses to build libindi support into KStars because libindi is too old.

Expected results:
libindi 0.6.1 available.

Additional info:
See: http://websvn.kde.org/?view=revision&revision=1110232

--- Additional comment from fedora-triage-list on 2010-07-30 08:54:11 EDT ---


This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

--- Additional comment from kevin.org on 2010-08-19 05:47:12 EDT ---

Ping? Sergio, are you still alive? Do you agree if we handle the upgrade to make kdeedu happy?

--- Additional comment from updates on 2010-08-21 08:25:10 EDT ---

libindi-0.6.2-1.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/libindi-0.6.2-1.fc14

--- Additional comment from sergio.pasra on 2010-08-21 08:27:14 EDT ---

libindi 0.6.2 built in rawhide and f14

--- Additional comment from updates on 2010-08-23 15:01:47 EDT ---

libindi-0.6.2-1.fc14 has been pushed to the Fedora 14 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 libindi'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/libindi-0.6.2-1.fc14

--- Additional comment from updates on 2010-09-01 01:52:48 EDT ---

libindi-0.6.2-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 1 Rex Dieter 2010-10-11 14:41:36 UTC 
We'd like this soon on f13 if possible, to prepare a kde-4.5.x update for f13.
Comment 2 Fedora Update System 2010-10-11 16:18:14 UTC 
libindi-0.6.2-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/libindi-0.6.2-1.fc13
Comment 3 Fedora Update System 2010-10-14 06:35:59 UTC 
libindi-0.6.2-1.fc13 has been pushed to the Fedora 13 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 libindi'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/libindi-0.6.2-1.fc13
Comment 4 Fedora Update System 2010-11-03 21:07:56 UTC 
libindi-0.6.2-1.fc13 has been pushed to the Fedora 13 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.